Re: A3000 Floppy Boot
- From: Jimmy <Jimmy@xxxxxxxxx>
- Date: Sun, 15 Jan 2006 07:57:13 -0000
"Warya" <warya@xxxxxxxxxx> wrote in
news:qYiyf.68366$Lb1.634@xxxxxxxxxxxxxxxxxxxxxx:
> The Hard drive boots fine. Starts up just like its supposed to. I'm
> just trying to figure out a way to keep the HD from trying to boot the
> OS from the HD after the ROMs kick from the HD. Darnit I should
> bought those A3000 ROMs from Italy on eBay when I had the chance! :(
>
> "Jimmy" <Jimmy@xxxxxxxxx> wrote in message
> news:Xns974AF3DED3529IfoundMe4@xxxxxxxxxxxxxxx
>> "Warya" <warya@xxxxxxxxxx> wrote in news:1137187045.511138.182860
>> @g44g2000cwa.googlegroups.com:
>>
>>> This is a continuation of my other A3000 Post, but it takes a
>>> slightly new direction. After learning from the amiga.hardware and
>>> the amiga.marketplace newsgroups, if I heard correctly, that the
>>> kickstart files have their own partitions. I have concluded that the
>>> problem is in the OS section of the HD as the kickstart files work
>>> without a hitch.
>>>
>>> My question is How do I set the Boot Priority so that the HD
>>> partition that's errored out has a lower priority than the floppy so
>>> that I can boot from the floppy?
>>
>> I have been watching this thread and now have the time to respond.
>> From the first I believed that what you have is a hard drive that is
>> going bad or suffering from "stickdum". Stictdum is where a hard
>> drive starts sticking so it takes longer to boot up. In short it is
>> time to replace your hard drive. Or possably the hard drive is
>> invalid.
>>
>> Next 1.4 roms (which you obviously have) are hard coded to read a
>> file in WB_2.x drive and DEVS directory named KICKSTART. Failing to
>> read that file in that directory on that device name it will try to
>> read the floppy drive for the kickstart file failing that it will
>> display the kickstart screen. It should be noted that reading of the
>> kick file only occures with a HARD reboot and not a soft reboot.
>> There for you could use your kickstart disk to load the kickstart
>> then remove the floppy and do a soft reboot (three fingered solute)
>> and you should boot from your hard drive if it has started spinning
>> by then or is not invalid.
>>
>> Also note that the DEVICE name must be "WB_2.x" the volume name can
>> be anything (I believe). Device names are those that you assign using
>> HDToolBox and volume names are those that you assign using workbench
>> meaning those that you see on workbench.
>>
>> The file can be any A3000 kickrom file meaning it can be 1.3, 2.04,
>> or 3.1. A 3.1 file must have come from a developer CD (as was stated
>> by someone previously) or can be a grabbed rom from an A3000 that
>> actually has a real 3.1 rom in it. But it MUST be an A3000 kickrom!
>> The kickroms for other Amigas such as an A500, A600, A1200, or A4000
>> will not work! The A3000 is the real special one of the Amigas and
>> had there own version of roms to handle the scsi controller.
>> (Actually I think that the rom from an A600 will work but I am not
>> sure) You could write an elabrate script that would ask which rom you
>> wanted to boot in to that would then rename the kickstart file in
>> DEVS and do a hard reboot then well you get the picture. I actually
>> wrote one of these scripts at one point but it was long ago and very
>> complexed.
>>
>> The short way to fix your problem (I believe with out actually seeing
>> what is going on) is to replace your hard drive. Short of that you
>> could power on then watch the hard drive activity light and make sure
>> that the drive is spinning up then do a soft reboot as many times as
>> it takes to boot.
>>
>> There is one other posibility besides a hard drive that is going bad
>> and that is an invalid hard drive. To check this you would need to
>> load the kickstart from floppy and the boot from a disk so you could
>> check the hard drive with a disk doctor of some type. But you should
>> know if it is an invalid hard drive right off because when you boot
>> from floppy the hard drive light should almost stay steady for quite
>> some time. This will be the OS trying to validate the hard drive. If
>> this is happening DO NOT SHUT OFF THE A3000 UNTIL THE LIGHT GOES OUT!
>> Stoping a validation process really screws up a hard drive.
>>
>> As for the next post from Mike, yes you can set the priority lower on
>> the hard drive or you can make the hard drive a non-boot drive using
>> HDToolBox. But who would want to do that just to load a kickstar file
>> or choose where to boot from when you simply have to hold down both
>> mouse buttons to get to the kickstart screen or boot screen. And you
>> are already getting to the the kickstart screen without messing with
>> HDToolBox. Now once the kickstart file has been loaded (from floppy
>> or from hard drive) you simply need to hold down both mouse buttons
>> again AS SOON AS THE REBOOT TAKES PLACE (assuming you kickstarted
>> 2.04 and not 1.3) to get to the boot up screen where you can choose
>> where you want to boot from.
>>
>> Good luck.
If you reread what I said I told you how to choose where you wanted to
boot the OS from. Simply keep both mouse buttons depressed when the
reboot occures after loading the kickstart. Reread my last paragraph.
.
- Follow-Ups:
- Re: A3000 Floppy Boot
- From: WARYA
- Re: A3000 Floppy Boot
- References:
- A3000 Floppy Boot
- From: Warya
- Re: A3000 Floppy Boot
- From: Jimmy
- Re: A3000 Floppy Boot
- From: Warya
- A3000 Floppy Boot
- Prev by Date: Re: A3000 Floppy Boot
- Next by Date: Re: A3000 Floppy Boot
- Previous by thread: Re: A3000 Floppy Boot
- Next by thread: Re: A3000 Floppy Boot
- Index(es):
Relevant Pages
|
