A2000

[just4funuk]

Glitch

Have to be honest didn't know there was an install disk as have two sets of Workbench 2.05 and both only have Workbench,Extras and Fonts.So thought I had a full set of  Workbench 2.05 disks.Thanks for the info.


TjLaZer

Hitting escape had no effect all I can say is I get a Fast kick loading screen when it boots.Holding right  mouse button while booting brings up a Fusion forty control menu SetFF operation NOFASTKICK or exit below this greyed out are the following options FastKick with a tick instpack no tick and diagnostic.Then below this is a cancel button which exits the menu.TjLazer thanks for the link to th eproms but dont have anyway at present of using them rom images.So with the infomation you have supplied think I will try to get either Workbench 2.05 or 2.1 installed on it corrcetly.

[glitch]

Hi,

     Yes, I believe it was either a four or five disk set  You should try to hunt down the 2.1 version rather than 2.05 if you can.

Good luck!

[TjLaZer]

Oh sorry it is indeed the right mouse button on bootup.  Is there an about or something pr other button that will tell you the version of the PNG ROMs?  I know on the V3.4 there is and it will tell you the version.  If you are using Kick 2.x you don't really need the latest version really.  Just get your WB upto 2.1 and you will be all set.

[just4funuk]

Update

Problem was in startup-sequence and mountlist.
Copied Workbench 1.3 to machine and machine boots ok but shell causes machine to guru.

Copied Workbench 2.1 to machine wont boot so copied Workbench 1.3 startup-sequence and mountlist.

Machine now boots so far and have to type loadwb to finish startup-sequence as there is a reference in the startup-sequence to  run the command fastmemoryfirt which Workbench 2.1 does not seem to have in the c folder.
But it is present on Workbench 1.3 disk.

Have also managed to get my idefix97 install so also have access to CDrom's now.

Also how do I assign the paths to tools

so the machine knows where  iconx is in c

Have just been altering the infomation on each app to point to dh0:c/iconx but there must be a way to make a link between :iconx = dh0:c/iconx so one assignment is enough.

thanks again for any pointers.

[Amiga4k]

You really need to start over, and properly install just one version of Amiga DOS. Ideally, as a minimum you need 2.04 ROM with AmigaDOS 2.1. In a pinch, you could use 2.05 ROM, without  a problem.
The problems your experencing are all based on an improper install, which will cause you future glitches. Format the partition, and re-install a proper set of disks.

[Oliver]

At some point in future you will probably also want to get the 3.1 ROMs, so you can run the more recent OS versions.

I also think you should definitely work on getting a complete set of WB disks.  I don't think your method to date will yield satisfying results.

If you particularly want to run an older OS, you can also run kick switchers, or softkickers, to give you access to an older kickrom set on demand.

Did you buy the A2000 with a bunch of floppy disks (I must have hundreds)?  When I bought mine, I was also missing some of the original install disks, but there were badly labled backup copies within the pile of floppies, so I use some original disks and some backups when installing the OS.  You may possibly have a similar situation.

[just4funuk]

Amiga 2000
Well after not much luck getting the older OS stable I decided pos to look at going for a newer kickstart OS installation and Brought OS 3.5 with the next step to buy the Kickstart Roms.But found out that the Fusion Forty would need New roms as well. Which I dont know how easy they would be to get and at what cost.Then would I have problems with ICDSCSI 2080 with Kickstart 3.1.

So am I wrong in thinking Workbench 2 will not install onto a A2000 with Kickstart 2.0 (37.175) roms and I need to look at installing either  Workbench 1.3 on currant setup or see if I can find a Kickstart 2.05 Rom and then try installing Workbench 2+.

Trying to locate a Full workbench set.But which version do you suggest I should be installing on A2000 with Kickstart 2.0 37.175.

Was thinking if I can get Kickstart 2.X installed and then poss use SKICK to run KIckstart 3.1 to see if Fusion forty and ADSCSI 2080 would work.If they do would then buy 3.1 kickstart chips and then installing OS 3.5 .

But first need to walk before I run so would like a stable OS installation on current setup.

 

[Argus]

Forget about SKick and the ICD 2080.  ICD used special memory buffering schemes to make their controllers faster. I just tried SKick with an ICD AdSCSI, no go.  Crashed on boot.  There are probably going to be problems with the Fusion Forty and SKick as well, because if it's an older FF, its own software will to a rom reboot, likely conflicting with SKick (though it may by a miracle work). I'd chuck the 2080 if it gives you any trouble and get instead a GVP HD+8 or even C=A2091.  These are true SCSI DMA controllers and *should* work fine with the FF (though you probably should upgrade the plug n' go roms with the latest version for compatibility with 3.1 system roms). Get the real 3.1 system roms for your 68040 boards.  See TjLazer for the latest FF roms.

[TjLaZer]

Yes I can burn the ROMs for you, see my site...

[just4funuk]

Thanks for the offer to supply Fusion Forty roms email sent.

[just4funuk]

Dreaming that maybe I might some day soon have


Amiga 2000 with Kickstart 3.1
OS 3.5 installed
1MB Chip
Fusion Forty with 18MB
ICDSCSI 2080
1GB HD
IBM CDrom

Running stable


Next step after above would be bigger harddrive.

[just4funuk]

Amiga 2000 now has Kickstart 3.1 roms installed.But still  having problems installing OS.

Installing the KIckstart roms has stopped the Accelerator working which was pointed out before and new roms will soon be purchased from TjLaZer.

But have tried to install OS 3.1 with Accelerator disabled and still have problem with startup sequence machine restarts.This is using the 3.1 install disk to install OS.

eplace  Start-sequence  with 1.3 start-sequence and machine will boot and fail.At prompt if I then type loadWB Workbench loads but all Software eg Iconx,multiview are not assined.

Has anynone got a good working 3.1 startup-sequence that will work with the ICDSCSI2080 Harddrive controller please post it on here so I can try it or tell me how to assign tools such as more,Iconx etc.

Thanks

[just4funuk]

Sorry about the Delay tjlazer

[just4funuk]

Ok the ongoing A2000 rebuild (I Wish I had never started)

Amiga 2000 already had
Amiga 2000 keyboard
ICDSCSI 2080  
Fusion Forty
Amiga 2000 Kickstrat 3.1 Roms
Fusion Forty Roms
Amiga Workbench 3.1
Amiga Workbench 3.5

Above purchased over last 9 months except actual amiga 2000 been sitting gathering dust for 2-3 years in bedroom.

Have now got

Amiga 2000
Kickstart 3.1 Roms
ICDSCSI 2080
Fusion Forty + 20MB Ram with new Roms (Workbench 3.1 now sees Fusion Forty again).(Thanks to TJlazer).

But still after trying to install clean installation of Workbench 3.1 I am still no nearer getting machine up and running. Have to laugh or would cry.

Wish I had just got an emulator (LOL)

Not had much free time to look at this at the moment.

Boots Ok from Floppy if stop ADSCSI auto booting (by holding mouse button on boot) .Can then mount the ADSCSI partitions after booting from floppy. But if try to boot from HD A2000 power light just flashes and machine just shows a guru message.

If anyone out there has a A2000 with ADSCSI card and FusionForty running Workbench 3.1 or 3.5 Please could you give me a copy of your startup-sequence as this is where mine is having the problem I suspect.




 

[Daedalus]

Hmmm... Sounds like a bit of a mess in there... Install disks aren't normally part of the Workbench disk set for some machines, so you're not necessarily missing them. It is fairly simple to set up the OS by hand, and all you'll need to do is modify your startup-sequence to get it to look in the correct places after you've copied everything from the floppies. Then it shouldn't ask for the floppies when you're booting.

If the drive's working fine after you boot from floppy, it does mean your controller and accelerator are getting on ok, and so once any special commands/libraries from the floppy are also on the HD there's no reason it shouldn't work the same way. Which leads me to suspect a filesystem mismatch somewhere. If you have a newer version of the filesystem on the boot floppy than you have in the ROM or the RDB, and it was formatted with the newer version, the older version will crash when it tries to mount the new version drive. As they can be stored in different places, you should find out what version is in each location. Can't remember the version that's in the 3.1 ROMs, but if any partitions are formatted with a newer version you'll have to have that version in the RDB as well. You can find the RDB version with HDToolbox and the one on the floppy by typing "version df0:L/fastfilesystem" in a shell window.

Could be way off the mark, but that's what this issue sounds like to me...

[just4funuk]

If Use workbench 3.1 startup-sequence machine gets stuck in loop.

If remove startup-sequence from HD0:s/

Machine boots from internal harddrive type loadwb and wb is loaded if
replace startup-sequence with one off ADSCSI installation disk
startup-sequence.hd saved to HD0:s/startup-sequence
machine will boot and fail on Fastmemoryfirst (Workbench 3.1 does not have this) Hence why it fails.

If then type Loadwb
WB loads.

Really do need to look at startup-sequence and see what in the workbench 3.1 version is causing machine to fail once this is removed from startup-sequence suspect machine will boot correctly and wont need any more editing.

Could be wrong
Wouldn't be the first time.


Watch out for next installment.