OS 3.9 installation issues

[dschallock]

I would try to eliminate as many variables as possible.  At one point was even thinking to suggest just getting that WarpEngine out of there and using the A3000's built-in 68030 and SCSI.  

*Although* having all the devices on the same chain probably wouldn't hurt. Does your WarpEngine use scsi.device?  Or something else?  (i.e., my GVP uses gvpscsi.device that's on a ROM on the board)

Edit:  This page lists an optional external SCSI connector.  Is that what you have?

Warpengine uses warpdrive.device.  My Hardrive is connected to it.
I don't have the official Macrosystems adpater, at least I don't think so.  I have an adapter Software hut sold me in the 90s along with an external drive case.  I used to run all the hard drives and cdrom and zip drive in an external mini tower.  Then the cdrom died.  I tried to move the whole system into a mirage elbox mediator tower and that whole set up never worked well, so I eventually put my amiga back together in the original case.  said to heck with the mediator angle and now I am working towards a xsurf set up.  I only recently purchased the external scsi cdrom drive I am using now. I think I will take pictures of everything this afternoon and post those too just so there is a clear picture of the set up.

[matthey]

Floppies suck. I have had horrible reliability problems with them as well (humidity?). It would be better if the hard drive had 2 bootable partitions, one with AmigaOS 3.1 and the other with AmigaOS 3.9. The boot priority can be changed easily in HDToolbox to select which one boots (or temporarily changed in the boot menu). Copy the AmigaOS 3.1 partition to the freshly (quick) formatted AmigaOS 3.9 partition, change the boot priority to boot off the AmigaOS 3.9 partition and install AmigaOS 3.9 from the CD-ROM. It may be easier to buy a newer and larger SCSI HD and save the smaller and older HD as a backup. The PFSAIO file system is probably worthwhile to use if getting and formatting a newer HD but it has a few quirks also.

A potential option for SCSI HD replacement:

http://eab.abime.net/showthread.php?p=1042839#post1042839

[SACC-guy]

Hahahaha... :lol: I'm putting you on the pay roll till I get this solved.  I promise to pay this forward to the community all jokes aside though.

@dschallock
SACC had a replacement floppy drive waiting for you at our last meeting...as discussed and as requested...sigh

BTW, our next meeting is this sunday 27th at 3pm (but some of us are meeting at 1pm)

[dschallock]

@dschallock
SACC had a replacement floppy drive waiting for you at our last meeting...as discussed and as requested...sigh

BTW, our next meeting is this sunday 27th at 3pm (but some of us are meeting at 1pm)

Hi Sacc-guy, thank for writing, and for having a drive I could try at the last meeting.  I'm sorry I wasn't able to attend that meeting.  I will try to attend this Sunday.  Thanks again for your support!

[Oldsmobile_Mike]

Hi Sacc-guy, thank for writing, and for having a drive I could try at the last meeting.  I'm sorry I wasn't able to attend that meeting.  I will try to attend this Sunday.  Thanks again for your support!

Oh heck, just bring your mess of stuff there, I'm sure they'll be able to get you sorted in no-time.  Sometimes 15 minutes hands-on is way better than 3 days back-and-forth on the forums.  :roflmao:

[SACC-guy]

@Olds...Mike
Just to prove a point, we did install 3.9 on a 4000 at the last meeting.

[dschallock]

Oh heck, just bring your mess of stuff there, I'm sure they'll be able to get you sorted in no-time.  Sometimes 15 minutes hands-on is way better than 3 days back-and-forth on the forums.  :roflmao:

Actually Mike this has been a great learning experience for me.  Sometimes the hard way is a great way to learn a lot and I super appreciate your help!

[SACC-guy]

Actually Mike this has been a great learning experience for me.  Sometimes the hard way is a great way to learn a lot and I super appreciate your help!

@ Olds-mike
I didn't mean to stop the fun!
@dschallock
Keep trouble shooting on the forums...we all learn more!!!

M

[Oldsmobile_Mike]

@ Olds-mike
I didn't mean to stop the fun!

I'm not stopped, just bogged down at work, but you know I still refresh this forum at least 50 times a day, haha.  

I'd say he's looking at two approaches:

(1) get that floppy drive from you
(2) disable the existing partitions or lower their priority to force the system to boot straight off DF2: with an ERD disk in the drive

I think I see OP's future, and it involves burning a few more ERD disks, just to make sure to get a good one.  

I was actually thinking it might be helpful just to throw a video together showing how to make one, for anyone who comes across this in the future, but don't know if I'll have time tonight/this weekend or not.  

[paul1981]

After some googling, I came across this thread which explains what ERROR #80000004 means: http://www.amiga.org/forums/showthread.php?t=11743

In Post #3 Piru mentions the following:

"Error 80000004 means CPU has executed illegal instruction (instruction is not identified by the CPU). The reason for this error can be numerous. In simplest case it's just some single program misbehaving, in worst case it's indication of a failing hardware."


I also found this thread which sounds a bit familiar (although it's an A4000): http://www.amiga.org/forums/showthread.php?t=49805

My guess is that you really need to copy the 68040.library from your WarpEngine disk to your Emergency Disk, because even though the version numbers are the same, the library might have been patched in order to work with the WarpEngine.

Try this first, and if it fails, you might consider following the instructions by Thomas in the above mentioned thread.

The version of SetPatch is at this point irrelevant - the problem is that your ROM-Updates file is corrupt. The thing in DEVS: This needs replacement with a version with a proper checksum. (-:

I'd look into these suggestions first.

[dschallock]

(2) disable the existing partitions or lower their priority to force the system to boot straight off DF2: with an ERD disk in the drive

I think I see OP's future, and it involves burning a few more ERD disks, just to make sure to get a good one.  
[/QUOTE]

I made 2 ERD disks.  I made sure both have the 68040.library from the original warpdrive disk.  I went into HDToolbox and made workbench not bootable.  Both ERD disks are still crashing on startup citing the "setpatch" error.
Not sure what to try next.

[dschallock]

I'd look into these suggestions first.

Hi Paul, I am very grateful for your feedback.  I read through the whole thread you indicated and it seems the original member who was having the problem on that thread turned out his whole problem was bad ram sims.  I suppose I shouldn't rule that out completely, but I have never had any other issues  that would lead me to believe I have bad ram sims.

[dschallock]

The version of SetPatch is at this point irrelevant - the problem is that your ROM-Updates file is corrupt. The thing in DEVS: This needs replacement with a version with a proper checksum. (-:

Thomas, Thanks for your input too.  I'm not sure where to get a proper Rom-updates file.  The 3.9 disk doesn't have a non corrupt version when creating a Emergency boot disk?

[dschallock]

Just a thought I had. You mention that your CD-ROM uses scsi.device, isn't it possible that this some way conflicts with the scsi.device versions present in the OS3.9 ROM update? (which are meant for IDE controllers only)

When you boot with no startup sequence, what happens when you enter the following: SetPatch SKIPROMUPDATES "scsi.device"

Mike, I just wanted to report back on this request.  I think I must be typing it wrong because I get a error. here is a screenshot.



Although just to recap.  When I boot with no startup sequence all the setpatch versions work.  The stock 3.1 one, the one on my 3.9 disk (44.17) and also the version you uploaded for me (44.38). They all work if I boot with no startup sequence.  The whole checksum error thing was real, but that seems to be solved with the new floppy disk.  The setpatch crashes I get now are any version on a floppy disk that I boot from. (and I have confirmed that I am booting from the floppy by disabling the workbench partition).
Ideas?

[Oldsmobile_Mike]

Try:  setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT

(no quotes)

One other thought:  manually copy the "AmigaOS ROM Update" file from the CD onto the ERD.  But I think this is where your problem is - you've either got a scratch or degradation on your CD, or just incredibly bad luck with disks and floppy drives.  Work-arounds aren't the answer, you need to get this fixed right.

On the bright side, there's a copy of "AmigaOS ROM Update" inside BoingBag2.  So even if your CD is scratched or degraded, you could get it from there as an alternate source.  The downside is to extract that file from the BoingBag archive you need your Xad decompressors working.  And that's a whole other can of worms for you already.  It's a catch-22 at this point.  You need that file, but no way of getting it from either your CD or your BoingBags.  

[Oldsmobile_Mike]

Actually, edit the Startup-Sequence on the ERD and add those two items, if they aren't already in the line.

C:Ed text editor should be on there?  Of course now I'm home and left all my disks at the office, ugh!