bigbod@soafy.bhpese.oz.au (Rodney Coleman) (04/04/91)
A few days ago I posted this problem, but I dont think I explained it well enough and some of the people who replied (thanks!!!) misinterpreted the problem. The problem is: If I boot the Amiga 3000 (off the hard disk) using WB 1.3 (by holding down both mouse buttons and selecting "kickstart 1.3 from hard disk" then the 3000 boots WB 1.3 normally and everything look OK until I try to boot a floppy (ie. place a bootable floppy in drive df0: and do CTRL+AMIGA+AMIGA). When I try this I get a "NOT A DOS DISK IN UNIT 0" error all the time. I get this for commercial disks, as well as disks that I have formated (and installed) on this machine under WB 1.3. I thought about a corrupt kickstart file on my hard disk so I booted the 3000 using the Superkickstart disk supplied with the 3000 (by selecting "kickstart 1.3 from floppy disk" after powering up 3000 whilst holding down both mouse buttons). After kickstart is loaded, the familiar WB hand comes up, but when I insert a WB disk (a BOOTABLE workbench disk), I get the above error (even with the Workbench 1.3 disk supplied with the Amiga!!) I have had the OBESE AGNUS checked, the FAST ram, and the 2nd meg of CHIP ram checked by a service centre. They are also at a loss to explain the problem. Does anyone have any ideas what might cause this problem?? Note that none of this happens if I boot WB 2.0 instead!! Thanks in advance for any help.... Rodney Coleman BHP Information Technology Newcastle Australia (049) 402139
dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) (04/05/91)
In article <1991Apr3.224147.25601@cerberus.bhpese.oz.au> bigbod@soafy.bhpese.oz.au (Rodney Coleman) writes: >A few days ago I posted this problem, but I dont think I explained it well >enough and some of the people who replied (thanks!!!) misinterpreted the >problem. The problem is: > >If I boot the Amiga 3000 (off the hard disk) using WB 1.3 (by holding down >both mouse buttons and selecting "kickstart 1.3 from hard disk" then the >3000 boots WB 1.3 normally and everything look OK until I try to boot a >floppy (ie. place a bootable floppy in drive df0: and do CTRL+AMIGA+AMIGA). >When I try this I get a "NOT A DOS DISK IN UNIT 0" error all the time. I >get this for commercial disks, as well as disks that I have formated (and >installed) on this machine under WB 1.3. > >I thought about a corrupt kickstart file on my hard disk so I booted the 3000 >using the Superkickstart disk supplied with the 3000 (by selecting "kickstart >1.3 from floppy disk" after powering up 3000 whilst holding down both mouse buttons). After kickstart is loaded, the familiar WB hand comes up, but when >I insert a WB disk (a BOOTABLE workbench disk), I get the above error (even >with the Workbench 1.3 disk supplied with the Amiga!!) > >I have had the OBESE AGNUS checked, the FAST ram, and the 2nd meg of CHIP >ram checked by a service centre. They are also at a loss to explain the >problem. Does anyone have any ideas what might cause this problem?? Note >that none of this happens if I boot WB 2.0 instead!! > >Thanks in advance for any help.... Rodney Coleman > BHP Information Technology > Newcastle Australia > (049) 402139 We are having the same exact problem with out A3000. Sometimes the disk icon says 'copy' instead of empty or whatever. It would not read a Chessmaster 2100 boot disk, although it read the data disk. And this disk is not supposed to be copy protected, anshould work on 2.0 or 1.3. I had a RAD: installed on 2.0 and 1.3, and removed it. After that the 1.3 kickstart booted off the hard drive once and never came back since then... The worst part is that the A3000 is back home, and I am at school. So it is hard for me to tell my brother (Amiga novice) how to fix it. By the way, is any one at SUNY Oswego an Amiga user? That would be the best way to help out my brother since I won't be there. Also, why does the A3000 GURU so much ?! -- David Tiberio SUNY Stony Brook 2-3481 AMIGA DDD-MEN -- Any students from SUNY Oswego? Please let me know! :)
jseymour@medar.com (James Seymour) (04/06/91)
In article <1991Apr4.195102.19233@sbcs.sunysb.edu> dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) writes: > > Also, why does the A3000 GURU so much ?! > Your question might better be phrased: "why does *my* A3000 GURU so much?!". I've owned my A3000 for some nine months now, and it has "GURU'd" on me *maybe* three times in all that time. Naturally, this does not count the times I've run bad code that I've written on it and crashed the machine. This is not for lack of use. While I haven't been running any high-end graphics intensive stuff on it, I have been running just about one of everything else on it on a regular basis - commercial and PD. Now, as to why *your* machine crashes "so much"? Don't know. What I *do* know is that there's a whole lot of not very robust software out there. Maybe you ought to re-consider some of the stuff you're running. I know this line is beginning to verge on .advocacy, but I've seen this type of comment re: the A3000 before and want to put it to rest. The A3000 does not "GURU a lot". At least that's been my experience. >-- >David Tiberio SUNY Stony Brook 2-3481 AMIGA DDD-MEN > -- Any students from SUNY Oswego? Please let me know! :) -- Jim Seymour | Medar, Inc. ...!uunet!medar!jseymour | 38700 Grand River Ave. jseymour@medar.com | Farmington Hills, MI. 48331 CIS: 72730,1166 GEnie: jseymour | FAX: (313)477-8897