Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: r6stu on October 06, 2007, 09:51:18 PM
-
For some reason my A1200 wont boot the 1st time. The HDD lights flash like the unit is loading but then just stops.
When I reboot the A1200 it boots fine. its just the 1st boot normally.
-
Your hard drive probably doesn't spin up in time for Kickstart to check whether it's there. By the time you reboot, it has spun up and is then detected.
I have heard that cutting pin 1 of the HDD cable can stop this happening, but I've never actually tried it.
--
moto
-
CUT the PIN 1??? lolol don't say, if you cut that you can't use the disk, try to disconnect the ide cable and turn on the Amiga, if run ok, test the hdd on another computer and what append.
-
1NOM155 wrote:
CUT the PIN 1??? lolol don't say, if you cut that you can't use the disk
Rubbish. Pin 1 is just the reset line. The disk will work perfectly fine without it.
This thread (http://groups.google.co.uk/group/comp.sys.amiga.hardware/browse_frm/thread/3b185735d41b4a0e/7b61133fa6f65ebd?hl=en&lnk=gst&q=help%3A+pin+1+on+ide+interface+cut&rnum=1#7b61133fa6f65ebd) confirms that the drive *will* work without pin 1 connected, but it sounds like it won't work in this case. After reading that thread it seems that cutting pin 1 just prevents drives from spinning back down when the Amiga is reset. It won't help if they don't spin up quickly enough in the first place.
@OP
You may want to try upgrading to Kickstart 3.1 if you haven't already, since it introduces a longer boot delay which may give your drive enough time to spin up before Kickstart gives up.
--
moto
-
Im running OS3.5. I dont get the kickstart prompt. it starts to boot from the HDD and dose so for the first 5 seconds, then stops on a black screen! :-?
Upon rebooting its fine.
-
r6stu wrote:
Im running OS3.5. I dont get the kickstart prompt. it starts to boot from the HDD and dose so for the first 5 seconds, then stops on a black screen! :-?
Upon rebooting its fine.
Oh that's totally different then. Can you post your startup-sequence and hardware config? If it hangs on boot the first time then works after a warm reboot then my gut feeling is that it's something to do with setpatch.
--
moto
-
I had this problem once and it was a problem with setpatch
Do a 1st boot with no start-up sequence and type setpatch in the cli and see if it cuts out.
Also as your running 3.5 its probably safe to assume you have more than a standard amiga. It might help if you say what upgrades and attachments your using.
-
I also think its setpatch, you could try it with options like SKIPROMUPDATES "scsi.device" or NOROMUPDATES
I'd avoid cutting line 1, it has caused me troubles
-
Is it save to try with SKIPROMUPDATES scsi.device? What if his HDD is on scsi.device? Maybe it would be better to just boot with no s-s and type "setpatch" to see what output you get. Remember that the default OS3.5/3.9 setpatch line in the s-s includes the "quiet" switch, which is why you don't get any output (even if it hangs or errors). Typing it from the CLI without the QUIET switch will allow you to see whether setpatch is successful.
Also, as I have said, cutting pin 1 of the HDD cable will not help in this case (now I understand fully what the problem is). However I would like to point out for the record that I had pin 1 cut on my old 3.0 A1200 and never had a single problem with it.
--
moto
-
I have std 2.5" IDE, HDD Blizzard 1220/4 RAM expansion, and Archos CDrom drive, with their cd drivers installed. and a network card sometimes.
I also notice that when the cd rom drive is connected it pauses, and reads the cd. I assume thats trying to boot from cd. Ill post a video up later.
-
r6stu wrote:
I have std 2.5" IDE, HDD Blizzard 1220/4 RAM expansion, and Archos CDrom drive, with their cd drivers installed. and a network card sometimes.
Do you have 3.1 ROM chips? Also you're right at the bottom of the system requirements for OS3.5. Maybe setpatch is having problems soft-kicking the ROM Update in to such a small amount of RAM? (It is enough, but Setpatch may be pausing with some warning which you can't see. This will be visible if you boot without s-s and just type "setpatch").
r6stu wrote:
I also notice that when the cd rom drive is connected it pauses, and reads the cd
That's normal. When Kickstart probes the IDE bus it looks at the CD-ROM drive to check whether it's a hard drive. The CD-ROM drive responds by spinning up its disc.
r6stu wrote:
I assume thats trying to boot from cd.
Technically, no it's not. It's just checking whether it's a hard disk.
--
moto
-
Ill do the vid later, yea KS31 roms, ill try the setpatch thing as well.
I should have my appollo 1230/50 soon as the strike is off, so will be sticking my os39 cd in to load that fresh!
Will update.
Cheers
-
#heres vid one: 1st boot
http://s145.photobucket.com/albums/r232/stuartkeith/?action=view¤t=MOV01112.flv
boot no ss
http://s145.photobucket.com/albums/r232/stuartkeith/?action=view¤t=MOV01113.flv
-
Are you using the light weight A1200 power pack?? I remember this causing similar problems. The solution was to use the brick sized one
-
What does the text say in the CLI window just before Workbench loads? Also, I couldn't see from the video but is the power LED on the A1200 repeatedly dimming and brightening when it's stuck on the black screen?
--
moto
-
Not sure what the text is. I thinks its somthing to do with an assign for a program ive moved/deleted, or for the AmiTCP bootup.
Im using an aftermarket Technoplus PSU to power it! I did have the golitath but the -5v went and the power light would just flash and screen go black.
-
First of all, comment out the "endcli" from the end of your Startup-Sequence by putting a semicolon at the beginning of the line. That will leave the window there and allow you to read the text to make sure it's not relevant to your problem.
If that doesn't turn anything up, boot with no startup-sequence and type "setpatch" then press enter and post any errors or hang you get.
--
moto
-
Mine is now doing this too. Is this normal for a flash disk? It's a minor hassle but just a tad annoying.
-
tokyoracer wrote:
Is this normal for a flash disk?
No.
--
moto