Workbench loading issues

[Laughy]

Hi,

Unfortunately I'm back with another problem!

Amiga is nearly back together, just on last stage of retrobriting the keys, some have taken 4 or 5 treatments, mainly the white keys. Still not quite there..

Anyway, have been playing a bit of Project X, had a funny thing happen, where it loaded a bit, then asked for Disk 4! Strange as it's only on two disks! Then noticed that I hadn't replaced the trapdoor expansion!

Put that back in, and Project X loaded ok.

Thought I'd try workbench to see if the memory expansion is registered. Unfortunately it no longer loads, it was fine just a couple of days ago, prior to keyboard being taken apart. All that has happened since is, I have cleaned corrosion off of floppy drive, and lightly oiled top of outer casing.

Just wondering if workbench not loading is a hardware issue? It does a few different things on loading.

e.g.

Loads a bit, then asks for the disk to be replaced in the drive. At the moment I'm unable to click retry, as my mouse is in bits getting cleaned up.

It loads and then looks as if a key has been pressed down, it's been a 1 and - so far, different each time. But it types about 2 and a half lines. Then stops, after a while the drive may turn a few times. But loads no further.

Could it be that I've been a bit clumsy and some oil or, dust has got into the drive, or would one of the CIA chips be faulty?

Thanks

[Oldsmobile_Mike]

Can you access the early startup menu?  Boot with no startup, and load your startup-sequence/user-startup/WBStartup programs one-at-a-time, see where the error is?  Obviously this will be pretty tough without a mouse.  :-/

[Laughy]

I'll put the mouse back together in the next hour or so.
I will need to be walked through your suggestion though, as I haven't used workbench for a long time, and am not sure how to go about doing any of those things.

[Laughy]

After loading for a while this is what I have on the screen.
[ATTACH]2861[/ATTACH]
It stopped loading. The disk not validated, you MUST replace workbench 1.3 on volume 0 appeared, then disappeared of it's own accord.

Then nothing happened for a few minutes while I took the photo. Then it does a lot more loading, but no change to the screen, except the cursor crept left across the screen!

[Oldsmobile_Mike]

You're booting from a hard drive?  Or floppy?

[Laughy]

Booting from the floppy, it's all I've got!

[Oldsmobile_Mike]

I'd start with the following:

- Inspect your work on reassembling the keyboard for any stuck keys, also check that connectors are tight, etc.
- Run a floppy drive head cleaner in your drive a few times
- Try booting with a different copy of Workbench disk, if possible

[GadgetUK]

I'd start with the following:

- Inspect your work on reassembling the keyboard for any stuck keys, also check that connectors are tight, etc.
- Run a floppy drive head cleaner in your drive a few times
- Try booting with a different copy of Workbench disk, if possible

I would check keyboard is put back together properly - you've not let water get in there have you?  ie after retrobrite you dried the keys, put spring under each key etc?  If you are testing with key caps off it will think you are pressing some of them.

Regards the floppy errors it sounds like the disk detect sensor is playing up.  Theres a pin switch that presses when the disk is it the drive, sometimes those switches need cleaning.  Also, the spring that pulls the mechanism closed when the disk is in sometimes weakens which makes it not pull the disk down onto the aforementioned switch.  Take drive lid off and see how it things are while its running - make sure disk mechanism is pulling disk down onto that switch.

I would clean the switches with WD40, but dont get it on the heads.

[danbeaver]

Mistaken "closed keys" as key presses can interrupt WB loading. This will ruin your day. Do everything to make sure the keys/pads are clean and dry, that the spring is working, and that there are no aberrant keys being closed.

You can check the disk drive loading by disconnecting the keyboard.

[Laughy]

Thanks,

Yes, it was the keyboard. I couldn't wait to test the memory, and the keys were still fizzing away!!

I'll try not to post anymore pointless queries! I'm just not that used to experimenting with my Amiga.

Loaded workbench with keyboard assembled, available memory was 887112, does that figure sound right for a half meg trapdoor expansion?

[Oldsmobile_Mike]

Loaded workbench with keyboard assembled, available memory was 887112, does that figure sound right for a half meg trapdoor expansion?

Close enough.  Workbench uses some of your available 1MB of memory when it loads.  You could try disabling any extras in your Startup-Sequence or running a two-color screen to squeeze a little more out.  

Glad you got the keyboard resolved.