Amiga 4000/40 boot-up issues

05 October 2014, 07:08

My A4000/40 (recently acquired) was working fine, but as of today seems to be booting to workbench (HD) then the cursor stays on the stopwatch permanently. You can move the mouse, but you can't click on anything because the cursor is stuck 'thinking'.

Someone suggested to comment out the user-startup from the startup sequence.

I gave that a shot (I'm assuming with semi-colon) but the same thing still occurs. There are no errors, etc, it just arrives at Workbench and sits there at the stop-watch. Any ideas people? It's a A4000/30 with an Opalvision graphics card.

hese · 05 October 2014, 08:01

This kind of behavior is seen when there is no floppy drive attached to the computer.
Check that the power and ribbon cables are well connected to the floppy drive.

You'll get pass that hangup also by temporarily disabling the floppy drive on the Early Startup Menu before booting to Workbench.

zipper · 05 October 2014, 11:14

Put set echo on as the first line of startup-sequence -perhaps you then can
see something. Or go straight to WB from Early Startup via assign Env: Ram: LoadWB Endcli and then try to run startup-sequence.

06 October 2014, 10:03

Thanks guys, I'll look into both of these possibilities and let you know

davideo · 06 October 2014, 11:43

When you say "permanently" how long have you left it sitting there?

It could be validating the HD which will take a loooongggg time.

31 July 2016, 01:31

I just removed a leaking battery from my A3000 and was getting the stuck stopwatch. I forgot to plug the cable into the floppy drive when I reassembled the computer. Thanks to Hese, It's working again.

05 October 2014, 07:08	#1
KKnD Posts: n/a	Amiga 4000/40 boot-up issues My A4000/40 (recently acquired) was working fine, but as of today seems to be booting to workbench (HD) then the cursor stays on the stopwatch permanently. You can move the mouse, but you can't click on anything because the cursor is stuck 'thinking'. Someone suggested to comment out the user-startup from the startup sequence. I gave that a shot (I'm assuming with semi-colon) but the same thing still occurs. There are no errors, etc, it just arrives at Workbench and sits there at the stop-watch. Any ideas people? It's a A4000/30 with an Opalvision graphics card.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Amiga 4000 will not boot after boing bag 2 update	sovietconscript	support.Apps	16	07 May 2019 11:26
sound issues on Amiga 4000	sovietconscript	support.Hardware	10	13 November 2012 15:07
Amiga 4000 boot problems with capacitors	Spirantho	support.Hardware	3	12 July 2012 18:07
N00b with a toaster 4000 (it's got issues)	bluegreengold	New to Emulation or Amiga scene	13	16 March 2012 03:06
amiga 4000/40 video issues	sovietconscript	support.Hardware	4	02 March 2012 21:03

05 October 2014, 08:01	#2
hese Registered User Join Date: Sep 2008 Location: Somewhere Posts: 223	This kind of behavior is seen when there is no floppy drive attached to the computer. Check that the power and ribbon cables are well connected to the floppy drive. You'll get pass that hangup also by temporarily disabling the floppy drive on the Early Startup Menu before booting to Workbench.

05 October 2014, 11:14	#3
zipper Registered User Join Date: Mar 2004 Location: finland Posts: 1,837	Put set echo on as the first line of startup-sequence -perhaps you then can see something. Or go straight to WB from Early Startup via assign Env: Ram: LoadWB Endcli and then try to run startup-sequence.

06 October 2014, 10:03	#4
KKnD Posts: n/a	Thanks guys, I'll look into both of these possibilities and let you know

06 October 2014, 11:43	#5
davideo Amiga Tomcat Join Date: Sep 2007 Location: Boston Lincs Posts: 1,500	When you say "permanently" how long have you left it sitting there? It could be validating the HD which will take a loooongggg time.

31 July 2016, 01:31	#6
AncientAmiga Posts: n/a	I just removed a leaking battery from my A3000 and was getting the stuck stopwatch. I forgot to plug the cable into the floppy drive when I reassembled the computer. Thanks to Hese, It's working again.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)