Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: dschallock on September 22, 2015, 04:19:23 PM
-
First, thank you for helping me with this.
OldsmobileMike has already been helping me a ton with some private messages with advice, but I don't want to abuse his time either!
My System:
A3000 Super Buster 11. GAL chips recently replaced fixed garbled graphics.
Battery has been replaced with coin cell upgrade.
3.1 Roms
OS 3.1 Installed
Warpengine 3040 with 32 megs of Ram installed.
2 megs of chip. No zip ram on motherboard.
750 Meg Scsi hard drive attached to Warpdrive.device (the warpengine fast scsi II).
External Lacie CDROM Scsi attached externally to scsi.device (a3000 onboard scsi).
Currently I don't own a working internal floppy drive so I have an external Amiga floppy drive plugged into the external floppy port (DF2 on my system. works good)
PicassoIV graphics card.
AD516 Sound card
Personal Animation Recorder with IDE hard drive attached.
The Goal: 3.9 installation with all the boing bags successfully installed!
The Method: I was planning on following OldsmobileMike's awesome videos on doing this install but I have already run into some hickups.
What I did:
1) I inserted the 3.9 CD and first thing attempted to make a emergency install disk. Program returned successful creation message.
2) I try to boot with the emergency disk and I get a crash saying something about "setpatch" and string of numbers 00012020021 or something.
3) I make a backup of my entire Workbench partition to a folder on my Work partition.
4) I boot from the install disk of 3.1 and format the workbench partition.
5) I do a fresh install of of 3.1
6) I mount 3.1's CD0 with my appropriate scsi drive and unit number.
7) I insert the 3.9 install disk and run the installation "upgrade from 3.1 or blank partition". When it finishes, I install the internet software from the CD as well.
8) I reboot and insert a CD I have burned from my PC with the latest Picasso96 software as well as the Boingbag1, boingbag2, and boingbag3/4 combo. First thing I notice is that the files names on the CD are all truncated to names like boing~1. I was hoping the 3.9 install was going to fix this filename shortening issue but apparently not.
*** I also notice at this reboot that Amidock is crashing on reboot and not loading, but I click suspend instead of reboot and I can still access the system***
9) I attempt to unarc the picasso drivers and I get errors for some of the files as corrupt. If I click past the error messages most of it decompresses fine but some of it definitely had a problem.
10) worried about this corruption above, I opt to use my original picasso96 install disk and install the software so I can run a larger RTG screen mode. The software seems to install fine and I am on a larger screen mode. Amidock is still crashing.
11) I attempt to unarc the first boingbag 1 archive which of course is listed as boing~1 or something shortened like that. I run into the same issue getting system messages of some of the files being corrupted. Pressing "ok" through the process what I am left with is enough to launch the boingbag1 installer but it asks me for the 3.9 cd to be inserted and as soon as I insert it the installer crashes and says there is something wrong with my install files (I'm sure its the corrupted files).
So, now I am not sure what to do. I can't install 3.9 on a freshly formatted partition because the disk fails to make an emergency install disk crashing on setpatch. Installing over a fresh 3.1 doesn't seem to be a good option either as I have amidock crashing right out the gate. My CD Rom has been working flawlessly in the past when installing Amiga software (like photogenics for instance... I installed that last week and got no errors), but CD's that I burn on the PC with amiga files I need seem to all get their names messed up and files seem to be corrupted on all the archives I burn. Not sure if this is related to the filename issue, or something else entirely. I apologize for typing so much but I wanted to give as much information as possible.
Thank you again for any help you can offer to help me get through this OS upgrade.
-Dan
-
I suppose that your WarpEngine needs a special version of 68040.library and most if not all of your crashes are caused by using the Commodore version of the library. Or none at all.
Actually I wonder what makes you think that OS 3.9 could run well from harddisk when it fails to run from floppy/CD. "Installation" of OS 3.9 does nothing else but copy files from CD to harddisk. The same files which failed to run before.
-
Thomas, Thanks for the tip on the warp engine 68040 library, I will definitely check that.
In terms of the Hard disk install Vs. CD. I never tried to boot from the CD and had that fail. I tried to create an emergency boot floppy and that failed. I didn't assume that meant that entire OS3.9 install CD was flawed, should I have?
-
First, thank you for helping me with this.
OldsmobileMike has already been helping me a ton with some private messages with advice, but I don't want to abuse his time either!
My System:
A3000 Super Buster 11. GAL chips recently replaced fixed garbled graphics.
Battery has been replaced with coin cell upgrade.
3.1 Roms
OS 3.1 Installed
Warpengine 3040 with 32 megs of Ram installed.
2 megs of chip. No zip ram on motherboard.
750 Meg Scsi hard drive attached to Warpdrive.device (the warpengine fast scsi II).
External Lacie CDROM Scsi attached externally to scsi.device (a3000 onboard scsi).
Currently I don't own a working internal floppy drive so I have an external Amiga floppy drive plugged into the external floppy port (DF2 on my system. works good)
PicassoIV graphics card.
AD516 Sound card
Personal Animation Recorder with IDE hard drive attached.
The Goal: 3.9 installation with all the boing bags successfully installed!
The Method: I was planning on following OldsmobileMike's awesome videos on doing this install but I have already run into some hickups.
What I did:
1) I inserted the 3.9 CD and first thing attempted to make a emergency install disk. Program returned successful creation message.
2) I try to boot with the emergency disk and I get a crash saying something about "setpatch" and string of numbers 00012020021 or something.
3) I make a backup of my entire Workbench partition to a folder on my Work partition.
4) I boot from the install disk of 3.1 and format the workbench partition.
5) I do a fresh install of of 3.1
6) I mount 3.1's CD0 with my appropriate scsi drive and unit number.
7) I insert the 3.9 install disk and run the installation "upgrade from 3.1 or blank partition". When it finishes, I install the internet software from the CD as well.
8) I reboot and insert a CD I have burned from my PC with the latest Picasso96 software as well as the Boingbag1, boingbag2, and boingbag3/4 combo. First thing I notice is that the files names on the CD are all truncated to names like boing~1. I was hoping the 3.9 install was going to fix this filename shortening issue but apparently not.
*** I also notice at this reboot that Amidock is crashing on reboot and not loading, but I click suspend instead of reboot and I can still access the system***
9) I attempt to unarc the picasso drivers and I get errors for some of the files as corrupt. If I click past the error messages most of it decompresses fine but some of it definitely had a problem.
10) worried about this corruption above, I opt to use my original picasso96 install disk and install the software so I can run a larger RTG screen mode. The software seems to install fine and I am on a larger screen mode. Amidock is still crashing.
11) I attempt to unarc the first boingbag 1 archive which of course is listed as boing~1 or something shortened like that. I run into the same issue getting system messages of some of the files being corrupted. Pressing "ok" through the process what I am left with is enough to launch the boingbag1 installer but it asks me for the 3.9 cd to be inserted and as soon as I insert it the installer crashes and says there is something wrong with my install files (I'm sure its the corrupted files).
So, now I am not sure what to do. I can't install 3.9 on a freshly formatted partition because the disk fails to make an emergency install disk crashing on setpatch. Installing over a fresh 3.1 doesn't seem to be a good option either as I have amidock crashing right out the gate. My CD Rom has been working flawlessly in the past when installing Amiga software (like photogenics for instance... I installed that last week and got no errors), but CD's that I burn on the PC with amiga files I need seem to all get their names messed up and files seem to be corrupted on all the archives I burn. Not sure if this is related to the filename issue, or something else entirely. I apologize for typing so much but I wanted to give as much information as possible.
Thank you again for any help you can offer to help me get through this OS upgrade.
-Dan
it's the old crappy 8+3 filename bs on pc. thats why its truncating the files. just copy the archives to the 3000 and rename them with .lha endings etc, then unarc them.
not sure why burning the archives to cd would have corrupted the archives though.
If you are burning os3.9 from a pc directly,it will corrupt the amiga file attributes i believe and cause havoc. i think you would have to burn the cd under a emulator or something or better yet buy a real os3.9 cd if you havent.
make sure the max transfer setting on the 3000 is set properly for the hd partitions.If its wrong larger archives may get corrupted when copied to the 3000.
Scsi termination and term power must be working/correct or you will have endless problems. Also double check warp engine jumpers.
to stop amidock from crashing, just remove it from wbstartup for now.
are you using a legit os3.9 cd or some junk you found on the net?
note that the initial install may be a tad flakey until at least boing bag 1 is installed, this is a known thing.
you might take a look at this:
http://www.gregdonner.org/os39faq/installtips.html
-
Thanks for the great reply Mechy. Couple of questions to your comments.
make sure the max transfer setting on the 3000 is set properly for the hd partitions.If its wrong larger archives may get corrupted when copied to the 3000.
Is the max transfer a value determined by the CDROM drive itself? Once I know that value do I add that to the CD0 Tooltype? I think it currently has ACTIVATE=1 DEVICE=SCSI.DEVICE UNIT=1
Scsi termination and term power must be working/correct or you will have endless problems. Also double check warp engine jumpers.
So I am working with 2 scsi controllers. The WARPDRIVE.DEVICE which has 1 hard drive attached, which is partitioned into WORK and WORKBENCH, and SCSI.DEVICE which is the CDROM attached externally. That CDROM has its own power supply, and scsi terminator attached. I assume that's all I need and all should be good..... I assume.
to stop amidock from crashing, just remove it from wbstartup for now.
Ok, will do.
are you using a legit os3.9 cd or some junk you found on the net?
note that the initial install may be a tad flakey until at least boing bag 1 is installed, this is a known thing.
Absolutely. I have real OS 31 disks, and 100% real OS 3.9 disk.
I was re-reading through my own process and one thing I think I should try again is to get a fresh solid 3.1 installation with the correct 040 library and the latest picasso96 software and then try to make my emergency disk from that.
2 unknown issues that are still freaking me out is:
1) Why was my emergency boot disk crashing because of SETPATCH? What is the setpatch thing even about, I never understood it, I don't know what could be going wrong or how to fix that.
2) Why am I getting corrupted files off my CD?
-
Is the max transfer a value determined by the CDROM drive itself?
MaxTransfer is for the hard drive. Shouldn't have to change anything for the CD.
Check your 3.9 CD for scratches or errors? You can't boot from the CD itself, need to boot from the recovery disk, but the old saying "garbage in, garbage out" - if it's copying damaged files from the CD it'll stop you right there.
And SetPatch does a lot of things, including enabling enhanced graphics modes, turning on processor caches, and loading various device drivers. I did a quick google search to see if I could find a full doc for it but nothing was coming up, but suffice to say, you need it. ;)
...more later, busy at work today. :(
-
Is the max transfer a value determined by the CDROM drive itself? Once I know that value do I add that to the CD0 Tooltype? I think it currently has ACTIVATE=1 DEVICE=SCSI.DEVICE UNIT=1
No. MaxTransfer is not related to any particular drive or harddisk. It is a workaround for buggy *host adapters*, not for devices. Hence, you only need a MaxTransfer if the device driver is not implemented properly, independent of what it is connected to. Unfortunately, most device drivers are faulty in this sense... omniscsi is probably one of the few non-broken ones. Hence, if you need one for your harddisk, and you have a CD connected to the very same host adapter, the CD drive needs exactly the same value because it sits on exactly the same host adapter. So I am working with 2 scsi controllers. The WARPDRIVE.DEVICE which has 1 hard drive attached, which is partitioned into WORK and WORKBENCH, and SCSI.DEVICE which is the CDROM attached externally. That CDROM has its own power supply, and scsi terminator attached. I assume that's all I need and all should be good..... I assume.
That is all you need, but in that case CDROM and harddrive are on two distinct controllers with two distinct "maxtransfer" requirements. Anyhow, in this particular case, I doubt that this is the cause for the problem because none of the files on the workbench and installation disk are long enough to fall into the max-transfer problem. As already suggested, the workbench.library from your 4000T installation disk should go into LIBS:, and this should be good enough to get a working workbench from the official 3.1 install disk. It won't overwrite a library it does not know, so the workbench.library will just stick there. 2 unknown issues that are still freaking me out is:
1) Why was my emergency boot disk crashing because of SETPATCH? What is the setpatch thing even about, I never understood it, I don't know what could be going wrong or how to fix that.
SetPatch fixes Os bugs, and amongst others, it loads the 68040.library for your system. This library has two specific purposes: First of all, the 68040 does not implement all documented 68K instructions, some FPU instructions are missing, and these missing instructions have to be supplied by software. This software (the Motorola FPSP - floating point support package) sits in the 68040.library. Second, the 68040.library also controls the MMU (the memory management unit), a function that lives for some 68040.libraries (as in "mine") in a separate library, the mmu.library. Now, this is the point where trouble begins because some (IMHO misdesigned) boards require a specific MMU setup without communicating this requirement properly to the operating system. Since the 68040.library (or the 68040.library via the mmu.library) is also responsible for programming the MMU, *some* specific boards require a *specific* 68040.library, and only the one from their specific vendor will work. Hence, if you use the original CBM 68040.library on a board that includes board components that do not behave according to the CBM specs, it will cause such a crash. And it is setpatch that crashes because setpatch loads this library. 2) Why am I getting corrupted files off my CD?
[/QUOTE] How did you burn the CD? The original CD should be fine, unless it aged and lost its content. If you burned the CD on a PC, then the PC will use a slightly different format than that understood by the Amiga. The original data CD-ROM specification alllowed only 8+3 file names, which is of course too constraining. Amiga defined a custom extension very similar to that used by Unix that simply writes more letters. Microsoft defined another incompatible extension ("Joliet") that causes the average Amiga CDROM handler to only see the backwards compatible part of the filing system, and hence only 8+3 file names.
-
UPDATE.
After watching all of Oldsmobilemike's videos on the install (thanks for making those by the way... super helpful), I restarted the process. I hit a snag again, but it happened at a very specific moment and so I thought I would post it as an update.
1) I reformatted partition workbench
2) I reinstalled os 3.1
3) I installed picasso96 and warpengine 68040 library. Got the screen resolution set correctly.
4) mounted CD0 correctly.
5) created the emergency boot disk from 3.9 CD and it worked! It boots. Everything great so far!
6) I reboot via the emergency disk. (no problems still).
7) I format partition workbench again so I could install 3.9 on a totally blank partition.
8) I reboot via the emergency disk as before and this time BOOM crash SETPATCH.
So something happened right there at that step that threw something off kilter. Any ideas?
Thanks!
-
Hey buddy,
A few quick thoughts on burning CD's. I use them all the time to transfer files to my A500 when I'm at home, since it doesn't have all the networking stuff I have in my 2000. Normally I use a recent version of Nero but I just tested and confirm correct operation using the built-in CD burning tools in Windows 7 Pro and being able to read-back in Amiga OS 3.9.
I'd start by re-checking all your settings, you may need to also edit your CD0 mountlist, but the only thing I ever had to change in mine was the specific device and unit ID. See attached screenshots, first three are from my PC, last two are of the identical files on my Amiga. Burned using the standard Windows tools onto a generic Maxell CD-R disk that I had kicking around in a drawer.
ProTip: when you use Nero you can make your disk "unfinalized" so you can copy a few files onto it, and then add a few more later, and a few more later, etc. I've got a couple CD's that I've used dozens of times to move many files from my PC to my Amiga. :)
See screenshots:
Edit - disregard that it says "3.1" in screenshot #4. MultiCX (which I use for editing part of my title bar) doesn't understand anything above that version. On my A2000 it totally flakes and just says "OS version ?.?". Haha. But it is 3.9. :)
-
UPDATE.
After watching all of Oldsmobilemike's videos on the install (thanks for making those by the way... super helpful), I restarted the process. I hit a snag again, but it happened at a very specific moment and so I thought I would post it as an update.
1) I reformatted partition workbench
2) I reinstalled os 3.1
3) I installed picasso96 and warpengine 68040 library. Got the screen resolution set correctly.
4) mounted CD0 correctly.
5) created the emergency boot disk from 3.9 CD and it worked! It boots. Everything great so far!
6) I reboot via the emergency disk. (no problems still).
7) I format partition workbench again so I could install 3.9 on a totally blank partition.
8) I reboot via the emergency disk as before and this time BOOM crash SETPATCH.
So something happened right there at that step that threw something off kilter. Any ideas?
Thanks!
Is the warpengine 68040.library on the emergency boot disk? Otherwise when you formatted the partition again, you lost it... just a guess.
-
8) I reboot via the emergency disk as before and this time BOOM crash SETPATCH.
Gah. Just saw this. Are you *sure* it's crashing at SetPatch? Have you turned on the feedback so that it displays each line as it executes?
Check the version of 68040.library on the disk?
Also it couldn't hurt to ask, what version of SetPatch? I believe the latest is 44.38 but that's installed in one of the BoingBags. I "think" 3.9 initially comes with 44.13. See the notes on the gregdonner webpage mentioned above for more info. Maybe try manually extracting one of the later versions (either 44.16 or 44.38) and replacing the version that's on the disk?
Is it something wrong with mounting the partitions after you've prepped them in HDToolbox? FFS, SFS, PFS, or something else?
Just throwing that out there, too many 16-hour work shifts in a row make my head foggy. :(
-
1) I reformatted partition workbench
2) I reinstalled os 3.1
3) I installed picasso96 and warpengine 68040 library. Got the screen resolution set correctly.
4) mounted CD0 correctly.
5) created the emergency boot disk from 3.9 CD and it worked! It boots. Everything great so far!
6) I reboot via the emergency disk. (no problems still).
7) I format partition workbench again so I could install 3.9 on a totally blank partition.
8) I reboot via the emergency disk as before and this time BOOM crash SETPATCH.
So something happened right there at that step that threw something off kilter. Any ideas?
Thanks!
Yes. 3.9 is not supposed to be installed on a blank partition. Otherwise, you're again stuck with the wrong 68040.library. Install it on top of the already installed 3.1. And thank P5 for their custom hardware requiring a custom library.
-
When I stopped using os 3.1's CD0 and installed the 3.9 CDROM software the CD started showing full file names which is great, but I can't seem to be able to properly extract any of the boingbags. Each one says the file "AmigaOS-Update" is corrupt and fails CRC check or something like that.
Thanks for the screen shots Mike, I am going to try using Nero and burning boing bag 1 already decompressed and see if it can read it that way.
Mechy, Yea I am using the warpengine 68040 library on the emergency boot disk.
oh.... so I tried 3 times to recreate the working emergency boot disk and I never got it to work again even though I followed the same steps. No matter what it always crashes on bootup on the Setpatch. I ended up just installing 3.9 over the fairly fresh 3.1 which worked mostly fine. I had to move amidock out of wbstartup cause it didn't like that. I want to try installing the boingbags now but I can't get a non-corrupted version off the CD. I'm gonna have to break down and buy a xsurf just to get this install going. :)
-
Yes. 3.9 is not supposed to be installed on a blank partition. Otherwise, you're again stuck with the wrong 68040.library. Install it on top of the already installed 3.1. And thank P5 for their custom hardware requiring a custom library.
3.9 is designed to be installed on a blank partition, there's tools for doing that right on the ERD and the CD. Problem is P5 and their custom hardware requiring a custom library not 3.9.
-
When I stopped using os 3.1's CD0 and installed the 3.9 CDROM software the CD started showing full file names which is great, but I can't seem to be able to properly extract any of the boingbags. Each one says the file "AmigaOS-Update" is corrupt and fails CRC check or something like that.
What tool are you using to extract them? Just use LHA.run from Aminet and extract them to RAM:.
-
Ok, so I switched to using nero on the pc to burn the CD and it solved the corrupt file problem.
I was able to decompress boingbag1 with no corrupt errors.
Now the problem is I start to run the update and I get XAD password errors. Unable to depack XAD missing password.
Any idea whats up with that?
-
Your other option if you are still unsuccessful in getting a working unarchiver over onto the Amiga-side:
Use WinRAR and unarchive all of them on a PC, then burn the unarchived contents onto a CD like this:
-
Now the problem is I start to run the update and I get XAD password errors. Unable to depack XAD missing password.
Any idea whats up with that?
Look for the file S:xadmaster.key
It should be on your OS3.9 CD and installed as part of the initial installation.
If it's missing look on the CD again. :)
-
I can't find the xadmaster key file anywhere on the OS 3.9 CD nor can I find it on my system. hmmmmm.....
-
I can't find the xadmaster key file anywhere on the OS 3.9 CD nor can I find it on my system. hmmmmm.....
Try this one. Second link from the top. Freely released by the author. It might not be "the" problem but it's certainly "a" problem.
http://www.vht-dk.dk/amiga/diverse/unsorted.htm
If that doesn't work I can send you a copy of mine in the morning. Go to sleep. :p
-
I could be mistaken, but I seem to remember reading that the WarpEngine is incompatible with the standard SCSI chip on the A3000, but will work with a .08 version SCSI chip.
-
Try this one. Second link from the top. Freely released by the author. It might not be "the" problem but it's certainly "a" problem.
http://www.vht-dk.dk/amiga/diverse/unsorted.htm
Thanks Mike, I downloaded it. I will try it when I get home from work today. Around 4pm California time.
If that doesn't work I can send you a copy of mine in the morning. Go to sleep. :p
Dude, you are so right, and I finally did go to sleep :insane:. Pounding my head against against my miggie till 2 in the morning and then having to be up at 5am for work. :rofl: hahaha... took me back to the 90's when I would work on my Amiga all night. Man, I never remember having so much trouble installing a version of Amiga OS though. I think I'm getting close. I wish I knew what was causing the setpatch error early on. My gut feeling is that setpatch thing is a root of some problem.
I could be mistaken, but I seem to remember reading that the WarpEngine is incompatible with the standard SCSI chip on the A3000, but will work with a .08 version SCSI chip.
Thanks for the feedback. I used to have issues using the standard scsi.device along side the warpengine.device but I thought those problems went away when I upgraded the superbuster chip. In any case, I don't think I'm getting any device errors from the 2 scsi controllers now. I was getting corrupted files from the CD, but I switched burning software on the pc and the corrupted files went away... so makes me believe the controllers are working ok on the Amiga.
-
OldsmobileMike, looks like the Xad keyfile didn't do the trick. Same errors saying I'm missing the password or key. Not sure if you have one I could try?
I'm still unable to make an emergency boot disk that I can actually boot from. It always crashes on the setpatch. I tried replacing the setpatch file and the 68040 file on the emergency floppy disk to see if that would help, but alas... nothing.
I'm starting to wonder if I will ever get a stable 3. install.
Thanks for the help all.
-
What version of SetPatch? Did you see note above about trying different versions 44.13, 44.16, and 44.38?
Could you post a screenshot of the exact xad message you're getting?
-
What version of SetPatch? Did you see note above about trying different versions 44.13, 44.16, and 44.38?
Could you post a screenshot of the exact xad message you're getting?
Yeah, when I get home today I am going to start over and this time I am going to stop at the first problem and post the screen shot and not move on until that problem is solved.
I downloaded a setpatch from the web yesterday along with what I believe to be the latest 68040 library, plus the latest picasso96 software. All of it was giving me problems last night. :eek:. The frustrating thing is that the problems don't seem to be consistent either. One time I did a fresh install of 3.1 over a freshly formatted workbench partition and then I installed the original floppy disk version of picasso96 and the original warpengine 68040 library and immediately made an emergency boot disk at that point. And it worked (meaning it booted without a setpatch error). But I have never been able to recreate that sequence again. I always get a setpatch error ever since. The one time it did work, I reformatted the workbench partition so I could do the 3.9 install on a fresh reformat and anyway after the format when I tried to double click on the install icon for 3.9 it asked me to re-insert the workbench drive. :madashell:.
I remember when I bought 3.9 when it first came out, I remember installing it as an update over my working 3.1 system and I don't remember things not working. I remember even amidock working out the gate. Now I do as clean an install as I can (over a fresh 3.1 install since I can't get a boot disk to work) and amidock is crashing right off the bat. Half the time I try to relaunch the 3.9 installer so I can install in the internet software too (Cause I watched your video and I know I need it so the boingbag updates can update it) and anway, half the time it gives me an "c/installer" crash. It's all pretty frustrating, and it probably doesn't help anything that I am still shaking the rust off my Amiga savvy-ness.
** I am super grateful to everyone here is helping me through this though! I think it would be too daunting to do this alone. **
I'll restart this afternoon after work, and I'll post exactly the first step. Versions I am using, and I'll include a screen shot of what is going on.
-
You need to figure out your SetPatch error, first. If you boot with no Startup-Sequence and just type in "setpatch", what happens? And which version? Be specific. :)
You might also want to throw away any of your old CD's that you burned with the program that was giving disc errors, and burn a whole new set of everything. Just to rule that out as a possible issue.
I don't know anything about what specific 68040.library you need for your card (I use THoR's libraries and they work great). I would say just start with whatever's on the install disk for your specific card. You have a WarpEngine, right? Then use these: http://amiga.resource.cx/install/WarpEngine.dms
You're right, it should not be this hard. But we suffer for our hobby, it's an act of love. :D
-
SetPatch is one thing, but what about the "AmigaOS ROM Update" file it uses, is it present in the Devs drawer of the Emergency Disk, and does it have the correct name? Also, I don't think using a different version of SetPatch is such a good idea, since it might lead to a conflict when SetPatch is run for the third time (from the CD) upon booting.
I have a feeling that using the default OS3.1 CD file system might be the root of your problems, since this will only use the 8.3 file & dir naming method, which leads to certain file names being truncated (and the extensions as well). This file system is only to be considered as a "better than nothing" type of solution. So after making sure that it's possible to access your AmigaOS 3.9 CD, you should have just copied the CacheCDFS file to the Devs drawer on your Workbench partition, and then tried to configure a proper mount file which uses it.
-
I don't think using a different version of SetPatch is such a good idea, since it might lead to a conflict when SetPatch is run for the third time (from the CD) upon booting.
I think he's using a 3.1 SetPatch in there, in conflict with a 3.9 SetPatch, or something. He mentioned "one he downloaded from the web", which could be anything, who knows? ;)
Tough to diagnose this problem until we start getting some actual version numbers and screenshots of the actual error message. ;)
-
OK... LETS DO THIS!
I reformatted Workbench.
I am now in installing 3.1
When that completes should I install the original picasso96 software and copy the 68040.library from the original warpengine disk before attempting to make a emergency boot disc?
I know we want to know setpatch version and to do the boot with no startup sequence and type setpatch and see what happens, so I will do that too and I will be specific! ;)
-
ok, we have a fresh 3.1 install
Here are the current versions installed presently.
Kickstart 40.68
workbench 40.42
setpatch 40.16
68040.library 37.30
I checked on the original warpengine floppy and the 68040.library is also version 37.30 so there is no point in copying since it appears the 3.1 install already has that version.
I mounted CD0 and from the shell checked some versions on the 3.9 install disc in CD0:EMERGENCY-BOOT/
setpatch 44.17
and apparently there is no 68040.library, at least not in the EMERGENCY-BOOT/LIBS/ folder.
So where should I go from here? Should I install the picasso96 software? Or should I go right to trying to create an emergency boot disc?
-
I suggest that you leave picasso96 for now. The main priority should be to create a working Emergency Disk, and then make a working AmigaOS 3.9 install.
-
ok, so I'll insert the 3.9 and attempt to make an emergency boot disk.
Here we go. :)
-
I think he's using a 3.1 SetPatch in there, in conflict with a 3.9 SetPatch, or something. He mentioned "one he downloaded from the web", which could be anything, who knows? ;)
I remember having similar problems years ago, where certain files was copied directly from the harddisk instead of the CD when creating the Emergency Disk. It might be possible that 3.1 SetPatch gets copied to the disk.
-
I remember having similar problems years ago, where certain files was copied directly from the harddisk instead of the CD when creating the Emergency Disk. It might be possible that 3.1 SetPatch gets copied to the disk.
Once the emergency disk is created I should be able to check the version of the setpatch on the floppy version the version on the os 3.9 cd. I assume it should be the newer 44.17 version I want the emergency disk, yes?
-
I checked on the original warpengine floppy and the 68040.library is also version 37.30 so there is no point in copying since it appears the 3.1 install already has that version.
This may sound overly paranoid, but there are at least six different authors of 68040 libraries. Cosmos, THoR, C=, P5, just off the top of my head. There was a survey posted here a few months ago that listed all of them, but damned if I can find it now. Just because the version # matches doesn't mean it's not different. I would err on the side of caution and copy the file off your install disk, just in case.
I would make the ERD disk and try to boot off it. Document exactly what happens. If it crashes on running SetPatch, try this version (rename your other one to .old so you can go back to it easily, if you have to):
-
Go back and read the gregdonner link (http://www.gregdonner.org/os39faq/installtips.html#1). There's five different copies included with 3.9. You want 44.16. No idea what 44.17 is, I wouldn't use it personally.
-
Once the emergency disk is created I should be able to check the version of the setpatch on the floppy version the version on the os 3.9 cd. I assume it should be the newer 44.17 version I want the emergency disk, yes?
Yes that's true. Do also check that the Libs/68040.library and "Devs/AmigaOS ROM Update" files are present on the disk as well.
-
):
Thanks Mike! Been waiting for you to link this version of setpatch all day! :banana:
-
Mike is probably right, it's the AmigaOS3.9:OS-Version3.9/Emergency-Disk/C/SetPatch file you want.
-
(http://www.danschallock.com/amiga/setpatch-crash.jpg)
Emergency boot disk gives me this on boot attempt. I will now try the version of setpatch you added Mike and report back. Thanks!
-
OMG, it just occurred to me. Are you using the same floppy disk for all of this? Is it some old disk you pulled out of a box that's 20+ years old? Try a different floppy and report back. :)
Also try booting with no Startup-Sequence and just run the setpatch command.
-
Ok, new version of setpatch gave me a recoverable error (the yellow one) first, and then booted to the same setpatch error crash as in the previous picture.
mike... hahahha... yes, of course I pulled that 20 year old floppy out of a box! :roflmao:. ok, I'll try a new floppy, and I'll also try the boot with no startup sequence thing too.
Ugh... I had to run out of the house for about an hour to drop someone off. If anyone is around in an hour, I will report the new findings out here. Thanks!
-
You know I'm going to ask you another dumb question here. You definitely have 3.1 ROM's, right? Not 3.0?
-
OMG, it just occurred to me. Are you using the same floppy disk for all of this? Is it some old disk you pulled out of a box that's 20+ years old? Try a different floppy and report back. :)
Also try booting with no Startup-Sequence and just run the setpatch command.
Real quick thought I better post this.
This is the boot with no startup sequence. tested set patch from the os 3.1 currently installed.
(http://www.danschallock.com/amiga/setpatch1.jpg)
And this is the same test trying to run setpatch from the floppy emergency disk.
(http://www.danschallock.com/amiga/setpatch2.jpg)
That um... checksum error thing.... :rofl: I suppose that is the old floppy thing you might be talking about Mike? :laughing:
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
OMG, it just occurred to me. Are you using the same floppy disk for all of this? Is it some old disk you pulled out of a box that's 20+ years old? Try a different floppy and report back. :)
Also try booting with no Startup-Sequence and just run the setpatch command.
(http://www.dogpictures.co/pictures/We_Have_A_Winner.jpg)
Way to hustle Mike!
Holy Sheet! What made you think of that?!!!
Must be on the hard stuff tonight eh!!!! :lol:
(http://www.crossedcomic.com/wp-content/uploads/2012/03/Cup-o-Kryptonite-Logo-300x264.jpg)
Wait a minute!!!!!
Did you go see the Pope today?
Did you get your Miggy Blessed!!!!!
:angel:
-
:laughing:
-
Two other thoughts: In your second screenshot it says 40.16. If you're booting off the 3.9 ERD It should be 44.16. Or 44.38, if you use the version I posted earlier.
Also here's what mine does. Just 'cause we're on the subject, not that it's very relevant. I hacked the sh*# out of mine though, with a string of LoadResident & LoadModule commands, and a lengthy "SKIPROMUPDATES" string, as well. One of these days I'll get around to joining the exclusive club of "I burn my own 3.9 ROM's too", but in the meantime that double-reboot doesn't bother me too much. ;)
-
Ok, I'm back. I'm going to get another floppy from my collection and see if we can get a different result. I still may have a xad key file issue when I get there, but... one thing at a time. :laugh1:
-
ok, new floppy.
Made another emergency boot disk.
This time when I boot with no startup sequence and then execute setpatch I don't get any more checksum errors. I looks like it works fine.
However....
Upon trying to boot from it, it still crashes on setpatch.
It has setpatch version 44.17 so maybe I'll try the version Mike sent me on this new floppy now.
-
nope. copied 44.38 version of the setpatch onto the emergency-disk floppy. Now when I boot I get a yellow recovery crash, I click the left mouse button, it continues and then I get the setpatch crash. :pissed:
I think someone mentioned checking romupdate files, I'm going to back read a little and try checking that I guess.
-
You know I'm going to ask you another dumb question here. You definitely have 3.1 ROM's, right? Not 3.0?
Yes, Definitely have 3.1 roms.
-
Yes that's true. Do also check that the Libs/68040.library and "Devs/AmigaOS ROM Update" files are present on the disk as well.
I just checked and both these are present on the disk.
(sigh)... I'm not sure what to try next honestly. I guess I could download the 44.16 version of setpatch and give that a go instead of the 44.38?
-
Are you sure your floppy drive is working okay? Did I read somewhere you mentioned something about your internal drive being toast, and that you are trying to do all this off an external DF2:?
You have any game disks or anything else you can try booting off of, just to give the drive a workout?
-
FYI here is the output of a straight SetPatch with no additional options or config changes. What it should look like, anyway. ;)
Yours crashed at console.device. Try this:
C:SetPatch SKIPROMMODULES console.device
Does it get past it then?
-
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"
-
When you boot with no startup sequence, what happens when you enter the following: SetPatch SKIPROMUPDATES "scsi.device"
Ha, was just going to post something about that, too. ;) Maybe his multiple SCSI controllers aren't playing nice with the updates?
Edit: I suppose you could also try "setpatch NOROMUPDATE" and then just add the updates back in one-by-one? But that would be a real PITA. :(
-
I'm still going back to your second screenshot in this post (http://www.amiga.org/forums/showpost.php?p=796282&postcount=44), however.
Can you tell us exactly what was happening there? You say you were trying to boot off your ERD? Because it says "SetPatch V40.16 already installed". 40.16 is a 3.1 SetPatch. Then it's giving a checksum failure on console.device 44.6, which a 3.9 update. No way are these two files going to play nice together...
-
Edit: I suppose you could also try "setpatch NOROMUPDATE" and then just add the updates back in one-by-one? But that would be a real PITA. :(
Yes that sounds like a tedious task indeed :)
I'm still going back to your second screenshot in this post (http://www.amiga.org/forums/showpost.php?p=796282&postcount=44), however.
Can you tell us exactly what was happening there? You say you were trying to boot off your ERD? Because it says "SetPatch V40.16 already installed". 40.16 is a 3.1 SetPatch. Then it's giving a checksum failure on console.device 44.6, which a 3.9 update. No way are these two files going to play nice together...
Maybe he was trying to run the EDisk SetPatch from within Workbench 3.1 instead of booting the floppy with no Startup-Sequence?
-
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.
-
I just checked and both these are present on the disk.
(sigh)... I'm not sure what to try next honestly. I guess I could download the 44.16 version of setpatch and give that a go instead of the 44.38?
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. (-:
-
Are you sure your floppy drive is working okay? Did I read somewhere you mentioned something about your internal drive being toast, and that you are trying to do all this off an external DF2:?
You have any game disks or anything else you can try booting off of, just to give the drive a workout?
Yes Mike, your correct. I have 2 different internal floppy drives that were both acting very buggy so I removed them. I am still on the hunt for a good internal replacement for DF0. In the mean time I have an external plugged into the the external floppy port, DF2. The boot priority is less on DF2 so when I try to boot from it I have to do the "hold down both mouse buttons on restart" and select DF2 as the boot device. I can certainly try booting from some games today when I get home. I have booted from some games off that drive in the past without a problem, but its good to rule everything out I agree.
-
FYI here is the output of a straight SetPatch with no additional options or config changes. What it should look like, anyway. ;)
Yours crashed at console.device. Try this:
C:SetPatch SKIPROMMODULES console.device
Does it get past it then?
The picture of the setpatch crash you are referring to was when I was using the buggy floppy disk. Once I changed the floppy disk to a better one and I boot with no startup sequence and run the setpatch it doesn't crash. But it DOES crash when I try to boot from it (Which makes no sense to me).
Having said all that, I will certainly try typing what you said and report the results.
-
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"
Ok, that is a good thought... I will try this too. :)
-
I'm still going back to your second screenshot in this post (http://www.amiga.org/forums/showpost.php?p=796282&postcount=44), however.
Can you tell us exactly what was happening there? You say you were trying to boot off your ERD? Because it says "SetPatch V40.16 already installed". 40.16 is a 3.1 SetPatch. Then it's giving a checksum failure on console.device 44.6, which a 3.9 update. No way are these two files going to play nice together...
Hi Mike, ok, here is what produced these two screen shots.
I had a fresh install of 3.1 and had created an emergency boot disk.
I booted the amiga with no startup sequence
In the first picture I had typed workbench:c/setpatch
Immediately after typing that (no reboot) I typed df2:c/setpatch The results were the 2nd screenshot.
Thanks again for all the help with this!
-
so when I try to boot from it I have to do the "hold down both mouse buttons on restart" and select DF2 as the boot device
Can you adjust your boot priorities of any other devices (hard drive partitions, etc.) to be lower, so you don't have to do this?
*SetPatch does make changes to the Early Startup Control screen that if you're having to go back into it each time, might be throwing something off...
*I vaguely seem to recall someone having a problem a long time ago where it would start to boot off the floppy, then incorrectly pull some of the files of the hard disk instead
*I wonder if they even considered the possibility that someone might try to install 3.9 off an external DF2:? I'll have to skim one of my ERD's later to see if there's anything off-hand that might have an issue with this...
TL;DR. I wonder if you shouldn't focus on getting all your hardware issues resolved before starting on software stuff? AFAIK I think you can still buy new internal floppy drives from AmigaKit; they won't match your faceplate but they'd work in a pinch. ;)
-
In the first picture I had typed workbench:c/setpatch
Immediately after typing that (no reboot) I typed df2:c/setpatch The results were the 2nd screenshot.
Okay, you know you're not supposed to do that, right? ;)
You need to reboot - boot off the ERD floppy disk. I'd get all your 3.1 partitions off there, clean slate. Or make them a lower boot priority so the system automatically goes to the floppy drive first.
-
So to reiterate: ERD floppy in DF2:. 3.9 CD in CD0:. Either lower the priority on all your other partitions so the system doesn't try to boot off them, or just go into HDToolbox and check the box to make them non-bootable. Power on. Don't touch anything. What happens?
-
So to reiterate: ERD floppy in DF2:. 3.9 CD in CD0:. Either lower the priority on all your other partitions so the system doesn't try to boot off them, or just go into HDToolbox and check the box to make them non-bootable. Power on. Don't touch anything. What happens?
Ok, but in terms of wiping out the 3.1 partition completely, I can't do that until I have made an emergency disk based on a fresh 3.1 install that has CD0 mounted... .yes? Then I can go into HDtoolbox and change the bootable thing, yes?
-
Ok, but in terms of wiping out the 3.1 partition completely, I can't do that until I have made an emergency disk based on a fresh 3.1 install that has CD0 mounted... .yes? Then I can go into HDtoolbox and change the bootable thing, yes?
Yes. You mean you don't have like 20 ERD's made, already? ;)
Just to make sure before you do that, you do have a working 3.1 Install disk with a copy of HDToolbox on it, right? (this is so you'll be able to change it back, if the other process doesn't work)
-
Yes. You mean you don't have like 20 ERD's made, already? ;)
Just to make sure before you do that, you do have a working 3.1 Install disk with a copy of HDToolbox on it, right? (this is so you'll be able to change it back, if the other process doesn't work)
Yes, I have my original 3.1 disks in the original 3.1 box I bought from an actual Amiga store in the 90s! :) I have been putting those disks through a work out this week. I have probably reinstalled 3.1 at least 12 times this week. :roflmao:
The Amiga store was Applied Computer Systems in Sacramento for history sake. I think the owners name was Jim if I remember correctly.
-
Man, now you've got me making ERD's, just for the hell of it. Just made one on my A500, worked fine. Good practice, I guess. Maybe I should mail you one, haha. :p
-
Man, now you've got me making ERD's, just for the hell of it. Just made one on my A500, worked fine. Good practice, I guess. Maybe I should mail you one, haha. :p
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.
-
I was just thinking... (dangerous I know). I think I have an adapter (its an adapter that goes from internal scsi 50 pin ribbon to external 25 scsi plug like my cdrom uses) that would allow me to get my external cd rom on the warpengine chain. Do you think I should do that if possible, or should I not add another variable at this point?
-
I was just thinking... (dangerous I know). I think I have an adapter (its an adapter that goes from internal scsi 50 pin ribbon to external 25 scsi plug like my cdrom uses) that would allow me to get my external cd rom on the warpengine chain. Do you think I should do that if possible, or should I not add another variable at this point?
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 (http://amiga.resource.cx/exp/warpengine) lists an optional external SCSI connector. Is that what you have?
-
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 (http://amiga.resource.cx/exp/warpengine) 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.
-
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
-
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
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!
-
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:
-
@Olds...Mike
Just to prove a point, we did install 3.9 on a 4000 at the last meeting.
-
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!
-
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
-
@ 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. :(
-
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.
-
(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.
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
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.
-
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?
-
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.
(http://www.danschallock.com/amiga/setpatch-scsi.jpg)
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?
-
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. :(
-
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! :(
-
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. :(
I'm assuming the xad thing is like a lha decompressor but with security measures built in? And I assuming me having my xad working is necessary because it confirms I actually have my purchased 3.9 cd in the drive at the time of unarchiving said boingbag?
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
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! :(
Add this:
setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT
To the startup-sequence on the ERD? ok, I can do that.
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
It's a decompressor library that works with many types of compressed file formats. They secured a license to include it with 3.9, but honestly the only thing I've ever used it with is the 3.9 Unarc program, and the "AmigaOS-Update" files for 3.9. Everybody else just uses LHA. ;)
-
Okay then...
I went back and read the entire thread because this last entry really lost me.
Maybe if you start (as Mike suggested) by using the Keep it simple idea?
My first question is do you have the red(1st) 3.9 cd or the pink (2nd and corrected) 3.9 cd.
It seems that everything is good from 3.1 (very good) but when you created the ER disk to boot 3.9 the items copied are getting in the way of a correct boot.
Our overall experience says to watch for well known issues. one of the first issues was the mistakes made on the install script on the red cd...
another was that some hardware was not good with the "newer" setpatch
another issue was that the cd driver was imcomplete sometimes...
sometimes the problems are from issues like the "scsi.device" instead of "warpscsi.device"
There's more... so start as simply as possible and keep it simple by keeping track of the changes you created with the hardware and software choices you made.
My fav problem was the asimware cdfs issue (grin)
-
in the startup-sequence on the ERD there is list of if statements. The last one says something like:
IF $scsiupdate EQ 1
setpatch QUIET
Are you saying I would modify this line to
IF $scsiupdate EQ 1
setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT
Or am I placing this line somewhere else in the startup-sequence?
-
Vacaville..to Washington DC..to Sacramento
How many amigas does it take to install an OS???
The boingbag1 and 2 do correct somethings but still need a booting 3.9 with a working cd reader.
I can't remember...is the cd connected to the 3000 scsi.device or the warpscsi.device?
-
in the startup-sequence on the ERD there is list of if statements. The last one says something like:
IF $scsiupdate EQ 1
setpatch QUIET
Are you saying I would modify this line to
IF $scsiupdate EQ 1
setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT
Or am I placing this line somewhere else in the startup-sequence?
Okay, if that's what it says (I left all my disks at the office), try:
setpatch SKIPROMUPDATES console.device,scsi.device QUIET
-
A screenshot of the decompressed BB2, for reference:
-
Vacaville..to Washington DC..to Sacramento
How many amigas does it take to install an OS???
At this point I could probably install this sucker in 15 minutes if I had it in front of me. And had a good DF0: floppy drive. And some known-good floppy disks. And a known-good 3.9 CD. :lol:
-
Okay, if that's what it says (I left all my disks at the office), try:
setpatch SKIPROMUPDATES console.device,scsi.device QUIET
That worked. It booted from the ERD. What does this mean, and should I proceed with a 3.9 install from here?
-
At this point I could probably install this sucker in 15 minutes if I had it in front of me. And had a good DF0: floppy drive. And some known-good floppy disks. And a known-good 3.9 CD. :lol:
Yes, i see that (really big grin)
-
Vacaville..to Washington DC..to Sacramento
How many amigas does it take to install an OS???
The boingbag1 and 2 do correct somethings but still need a booting 3.9 with a working cd reader.
I can't remember...is the cd connected to the 3000 scsi.device or the warpscsi.device?
the CD is connected the scsi.device and it is working. The external floppy drive is also working (I believe). The culprit I was having before is the fact that all my floppies are old and unreliable media at this point although I think I found a good one I working from now.
-
That worked. It booted from the ERD. What does this mean, and should I proceed with a 3.9 install from here?
It means exactly what it sounds like. That big "AmigaOS ROM Update" file in DEVS: contains updates to many of the files that are in your actual, physical ROM. Device drivers, handlers, libraries, stuff like that. By Default it tries to use the versions in the file on disk instead of the ones in your (older) ROM. SKIPROMUPDATES is telling it to use the versions in the ROM rather than the newer versions on the disk.
And, yes! What the heck, at this point. Proceed! Although keep in mind you may need to edit any startup-sequences it creates (S-S is updated with each BoingBag update, also), to keep adding those two commands. :)
-
That worked. It booted from the ERD. What does this mean, and should I proceed with a 3.9 install from here?
@dschallock
Yes, that's idea. IN order to get a complete 3.9 install, it requires booting from the er disk.
Do you have BoingBag 1 and BoingBag 2?
-
It means exactly what it sounds like. That big "AmigaOS ROM Update" file in DEVS: contains updates to many of the files that are in your actual, physical ROM. Device drivers, handlers, libraries, stuff like that. By Default it tries to use the versions in the file on disk instead of the ones in your (older) ROM. SKIPROMUPDATES is telling it to use the versions in the ROM rather than the newer versions on the disk.
And, yes! What the heck, at this point. Proceed! Although keep in mind you may need to edit any startup-sequences it creates (S-S is updated with each BoingBag update, also), to keep adding those two commands. :)
But did I understand you correctly before that perhaps the Rom update in boingbag2 might be a fix that I won't need to SKIP?
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
But did I understand you correctly before that perhaps the Rom update in boingbag2 might be a fix that I won't need to SKIP?
It might. Although the reason I was suggesting it was as an alternative source for a ROM update file, in case the file on your 3.9 CD was damaged/scratched/etc. ;)
-
At this point you've booted off the ERD with the 3.9 CD in the drive and gotten the "Boing ball" background screen and whatnot, correct? Here's where you'd prep a partition with HDToolbox, if you haven't already, and start the install. Go go go! :D
-
Mike,
I am checking on the warp dot device for install issues, I think if he keeps this card.
He will have to give up using the rom updates?
M
-
At this point you've booted off the ERD with the 3.9 CD in the drive and gotten the "Boing ball" background screen and whatnot, correct? Here's where you'd prep a partition with HDToolbox, if you haven't already, and start the install. Go go go! :D
3.9 has been installed successfully, along with the internet software and the cdrom software. :)
I am loading up the cd with the boingbags now....
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
Stay with the BB1 and BB2 for now.
There are other issues with 3 and 4
-
There are other issues with 3 and 4
Lies! :p :lol:
-
Lies! :p :lol:
Are you going to stay up all night and "fix" even more? (lol)
-
I'm backing up the workbench partition before installing anything else so I have a good save point in this game. :)
-
Are you going to stay up all night and "fix" even more? (lol)
Haha, that's a fair point. ;)
Although I run BB4+ on both my systems with zero issues, stable all day long. OP's mileage may vary. ;)
To clarify for OP: BB1&2 were released by H&P, as updates to the original 3.9 release. BB3/4 are more "community-sourced", in other words they were put together by Amiga enthusiasts and contain updates to drivers and libraries and other software, beyond what was available when BB2 came out (in 2002). So by installing 3/4 you're going to get a much more updated system, but maybe without the benefit of some of the more extensive testing H&P did.
My .02 cents, I would always install them, because I want my Amiga to have the latest and most up-to-date drivers and libraries. I haven't had any problems, maybe just needed a few tweaks to the Startup-Sequence for optimal performance. But some people are scared of new things (Russian proverb: "New is first enemy of old"), and would rather halt their progress with the "official" BB2 circa 2002. Or for some people making edits to Startup-Sequence is unfamiliar territory. Blah blah, try them, if it doesn't work just reinstall again, since now you know how to do it. ;) LOL
-
well it wont let me to the boingbag1 install because of the "xad missing password" error.
I copied the xad key file you gave me to my S drive and tried again but it didn't make a difference.
-
well it wont let me to the boingbag1 install because of the "xad missing password" error.
I copied the xad key file you gave me to my S drive and tried again but it didn't make a difference.
Gah.
Drop down to a command line and type:
version xadmaster.library full
Post the output.
-
Gah.
Drop down to a command line and type:
version xadmaster.library full
Post the output.
(http://www.danschallock.com/amiga/xadmaster-version.jpg)
-
Okay, that's an old version, but try the fix suggested in this post, instead:
http://eab.abime.net/showthread.php?t=31637
Copy the entire contents of the BoingBag archive from the CD into either RAM: or onto your hard drive somewhere, and run it from there. Keep the 3.9 CD in the drive.
-
Okay, that's an old version, but try the fix suggested in this post, instead:
http://eab.abime.net/showthread.php?t=31637
Copy the entire contents of the BoingBag archive from the CD into either RAM: or onto your hard drive somewhere, and run it from there. Keep the 3.9 CD in the drive.
I'm already running it from another partition. I could try RAM if you thought that was worth a try?
-
I'm already running it from another partition. I could try RAM if you thought that was worth a try?
Yes, copy the BB archive to RAM: and try to run it from there, with the 3.9 CD in the drive.
2nd option: manually extract the newer version of xadmaster.library from BB1 using Unarc and try sticking that in LIBS:.
-
How far into the installation process does it get before it gives you the error message? Can you post a screenshot?
-
same results running from Ram.
moving to second option.
its asking for a password to extract that one file (xadmaster.library)
do you know what that password is?
-
same results running from Ram.
moving to second option.
its asking for a password to extract that one file (xadmaster.library)
do you know what that password is?
Do you have the 3.9 CD in the drive? See post 2 & 5:
Read this thread. If it's not working with the CD in the drive try what's in post #20:
http://eab.abime.net/showthread.php?t=32233
-
well I had to follow what the other post said because nothing was working.
Basically I typed
xadunfile AmigaOS-Update "" PASSWORD=####### (I edited out the password just in case there is something wrong with posting it.)
And it worked in that it unpacked everything into the same directory but it still won't install with the installer. It still says its missing the xad password and aborts.
I know this boingbag1 works for alot of people, yourself included. In fact I watched it work on your video. I'm not sure what I've done different.
-
I know this boingbag1 works for alot of people, yourself included. In fact I watched it work on your video. I'm not sure what I've done different.
Do you have the 3.9 CD in the drive? Is it accessible?
Edit - I'm off to play some Cannon Fodder and pass out, it's 5am local time. I leave you with this link, for your amusement. :) http://mentalfloss.com/article/68779/12-secrets-your-companys-it-people
-
Do you have the 3.9 CD in the drive? Is it accessible?
yes sir! in the drive.
-
Mike you are amazing and I owe you a huge debt for getting me over the first major hurdle. We have 3.9 Installed.
-
Just to keep this message afloat to anyone with a magic trick. I am now stuck una let to install the first being bag. I have an original 3.9 disk (the pinkish one) and a fresh install of 3.9. I am unable to install the first boingbag because it fails citing xad missing password. It does read my cd in the drive and it does verify it is there, I know this because if I take the disk out it says it can't verify the 3.9. I put it back in and it wants to install business it hits the xad error. I have manually extracted the xadmaster. Library from boingbag1 using unarch and a password supplied on eab message board. It works and I can get the file but that doesn't fix the issue. Following another post on eab I extracted the whole amigaos-update file into the same directory and the boingbag and it's installer but same results. If someone knows another trick (I can't be the only one who had this issue) please let me know.
Thank you!
-
What tool are you using to extract the Boing Bag archives initially?
Are you getting a directory that matches my screenshot from this post (http://www.amiga.org/forums/showpost.php?p=796181&postcount=17)? How far does it get from when you click on "Installation" do you get the error?
-
What tool are you using to extract the Boing Bag archives initially?
Are you getting a directory that matches my screenshot from this post (http://www.amiga.org/forums/showpost.php?p=796181&postcount=17)? How far does it get from when you click on "Installation" do you get the error?
Hi Mike,
I re-did the boing process today and made sure I:
1) re-downloaded boingbag1 from the link you provided me.
2) unarchived using winrar and exacted to windows desktop
(http://www.danschallock.com/amiga/bbprob1.jpg)
3) Then I burned the extracted folders to CD.
(http://www.danschallock.com/amiga/bbprob2.jpg)
4) and then I copied to Ram on my hard drive and attempted to install.
Here is a video I shot of the attempted install so you could see the specifics. (https://youtu.be/k1gW1cOI05I)
Unfortunately the boingbag1 did not install citing the same xad password issue.
-
Gah. Probably not helpful but there's this thread:
http://www.amiga.org/forums/showthread.php?t=13274
(see the last comment where he says it worked from him with Dopus4 but not 5) (I would try just using straight LHA at the command line)
Try to re-download BB1 and unarchive it with LHA (into RAM:) rather than WinRAR?
Grasping for straws, now. Go to that meeting tomorrow! :)
-
I wish H&P or someone still supported BB1 and 2. Seems like I'm missing something obvious or crucial or both.
-
Gah. Probably not helpful but there's this thread:
http://www.amiga.org/forums/showthread.php?t=13274
(see the last comment where he says it worked from him with Dopus4 but not 5) (I would try just using straight LHA at the command line)
Try to re-download BB1 and unarchive it with LHA (into RAM:) rather than WinRAR?
Grasping for straws, now. Go to that meeting tomorrow! :)
I think their problem is different Mike. They were getting fatal errors on line 3. This xad password issue seems pretty specific. What's crazy is I can't seem to find anyone on a search who had the same issues as me with Boingbag1 anyway. Which makes me think I have something wrong with my setup or some component somewhere.
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
I wonder if you could decompress the archive with the password, and recompress it without password protection in its original location?
-
Copy the entire contents of the CD to a hard drive partition, and assign it there with the same name as the CD? So it can do its verification against the files there instead of a disc?
-
Copy the entire contents of the CD to a hard drive partition, and assign it there with the same name as the CD? So it can do its verification against the files there instead of a disc?
Yea, thats a good idea. I assume you mean the 3.9 disk. Yea I'll try that now.
-
Well that was a good try. It took a long time to copy the contents of the CD to the HD. I assigned AmigaOS3.9 to the directory that copied the contents to. I ran the boingbag1 installation script, it had no apparent problem with my assign, but alas it came up with the same xad password error.
So about that other idea where I unpack and repack without the password... I already have the AmigaOS update file unpacked. How would I repack it?
Another thought is to manually install the unpacked components if there is a list somewhere of what is supposed to be done. Is this a feasible idea?
-
Copy the entire contents of the CD to a hard drive partition, and assign it there with the same name as the CD? So it can do its verification against the files there instead of a disc?
Are you guys still at it? Get some rest...
BTW, I vote for a installer problem.
M
-
Well that was a good try. It took a long time to copy the contents of the CD to the HD. I assigned AmigaOS3.9 to the directory that copied the contents to. I ran the boingbag1 installation script, it had no apparent problem with my assign, but alas it came up with the same xad password error.
So about that other idea where I unpack and repack without the password... I already have the AmigaOS update file unpacked. How would I repack it?
Another thought is to manually install the unpacked components if there is a list somewhere of what is supposed to be done. Is this a feasible idea?
It verifies against the Video files on the CD, so copy the entire thing
-
Are you guys still at it? Get some rest...
BTW, I vote for a installer problem.
M
I've tried with the version of installer that comes with 3.9 and the version that comes inside the boingbag1 release. I haven't checked to see in the version of installer in boingbag2 is different or if it would yield different results. Is that what you mean but installer problem? The version of installer?
-
It verifies against the Video files on the CD, so copy the entire thing
HI Danbeaver, thanks for the feed back. I did make sure I copied the whole cd. Also I have seen what the installer does when it can't verify the CD. It pops up a message saying "can't verify the 3.9 cd".
In my case it checks the CD and doesn't seem to stop at that moment. I think it verifies fine. What happens next is it attempts to start unpacking the update with xad and it fails when it doesn't find some security password that i assume should be present on the CD? My logic tells me this is either a xad version issue (although I have tried several versions) or there is problem with my 3.9 cd and it's good enough to verify and install but it is missing the password boingbag 1 is looking for. I don't know.
-
Just for your info:
FAQ on Greg donner site:
http://www.gregdonner.org/os39faq/installtips.html
M
-
Sooo... Did you bring your system to the SACC meeting? How'd it go? :)
-
Sooo... Did you bring your system to the SACC meeting? How'd it go? :)
Yes, I did bring it. Great group of guys. Lots of help with my system is general. (I have a working internal floppy drive now).
In terms of the boingbag updates we had some success and but we aren't solved yet.
Sacc-guy had the official boingbag1 CD along with other goodies burned to disk. He was guessing I had a problem with my version of "installer". We tried swapping that version around. At first the version we added crashed completely. Then we switched to a version that no longer crashed but would fail to install the update from his official boingbag1 CD with the "failed at line 129" issue. However, when I ran the update from the downloaded version I got from you I would get the xad password error. Sacc-guy suggested I click "ignore all" to that error. Which I did. I appears to still have installed some parts of the boingbag update, but I don't believe it installed everything. When I type version workbench I get 45.2 which according to Sacc-guy meant I had boingbag2 installed but I don't think any of boingbag2 has been succesfully installed. When I try to run boingbag2 I just get a "failed, your file must be corrupt" message.
So, we didn't go backwards, I think some of boingbag1 was installed but I don't think all of it was.
I still would like to know if there is a list of what boingbag1 installs so I could go through manually and make the changes. I know it would be tedious but after this much time, I'm willing to do it. Hopefully then the boingbag2 would take.
-
You could extract BB1 and manually copy every single file over. It's a lot of stuff, and tedious.
Here's another idea: reinstall 3.9. Start fresh, again. Maybe there's something just downright broken in your 3.9 install?
-
You could extract BB1 and manually copy every single file over. It's a lot of stuff, and tedious.
Here's another idea: reinstall 3.9. Start fresh, again. Maybe there's something just downright broken in your 3.9 install?
yea, I could do that. If I do that I think I might try to put my cdrom on the warpdrive.device chain so they are all on the same chain.
The most dramatic option (and also something SACC-GUY suggested as a possible solution) was to take out my warpengine completely during the install and then add it after I get through boingbag4. Showstopping problem with that is I don't have any fast RAM on my amiga3000 mother board anymore. Only 2 megs of chip. The fast ram I have is 2 16meg simms on the warpengine. I doubt I could install 3.9 and boingbag1-4 all on 2 megs of chip ram. One thing is for sure, I feel like Ive crossed an effort level point of no return. I am definitely in this to win this at this point! :)
-
You could extract BB1 and manually copy every single file over. It's a lot of stuff, and tedious.
Here's another idea: reinstall 3.9. Start fresh, again. Maybe there's something just downright broken in your 3.9 install?
@olds-mike
I noticed two things I have no knowledge of...
He was using the PFS on sys:
and he was using two scsi controllers (scsi.device and warpscsi.device)
I was too too lazy to go to a bare 3000D...
another idea is to attach only to scsi.device on the motherboard and use the scsi rom updates? we didn't try that...
(I wanted to go home eat dinner and sleep.) grin
-
@dschallock
Because my H &P BB1 cd has never failed for me with my setups, (mostly 4000) I'm going to borrow a 3000D and go thru the steps on the 3.1 to 3.9 and BB1 and 2 and report back.
-
@dschallock
Because my H &P BB1 cd has never failed for me with my setups, (mostly 4000) I'm going to borrow a 3000D and go thru the steps on the 3.1 to 3.9 and BB1 and 2 and report back.
Thanks again for your help! I'm sorry I kept you as late as I did. Thanks again!
-
Thanks again for your help! I'm sorry I kept you as late as I did. Thanks again!
Da nada, amigo
-
What version of PFS are you using? There's a few different ones, cpu specific I believe. Can you shed any light on that? Might be worth while trying the whole install under good ol' FFS. Well, it's something else to try at least.
-
@olds-mike
I noticed two things I have no knowledge of...
He was using the PFS on sys:
and he was using two scsi controllers (scsi.device and warpscsi.device
If he's able to install the OS and run applications (I see Dopus and other things in his pics and vid) I'm assuming file system isn't an issue. I'd make sure you're installing the latest version of PFS3-AIO (http://aminet.net/package/disk/misc/pfs3aio) from Aminet along with the C: (or at least PFSformat) tools from the 53 install (http://aminet.net/package/disk/misc/PFS3_53).
I was pretty intimidated by PFS the first time I used it, as well, and found the lack of documentation daunting. But it's a good FS especially for "more advanced" Amiga's (i.e., I'd use FFS if if I was just building something to play games).
Will try to load mine up later and post a few screenshots of the settings that work for me (disclaimer: your mileage may vary). ;)
Two controllers shouldn't be an issue, but same as we've already talked about, may be simpler to eliminate as many possible causes of issues here as possible. Try them both on warpscsi.device. Hummm, I wonder if maybe there is some MaxTransfer or Mask issue... it validates the CD based on the video files on there, maybe it's having a problem reading those big files off it because those settings are off?
Post a screenshot of your CD0: device settings (the text file)?
-
I was pretty intimidated by PFS the first time I used it, as well, and found the lack of documentation daunting. But it's a good FS especially for "more advanced" Amiga's (i.e., I'd use FFS if if I was just building something to play games).
Actually, the documentation for PFS is good but it is technical and the installation process could be easier. I have had few problems with PFS but I have heard that it doesn't like a few hardware setups. I don't know if this has been improved with PFSAIO.
-
Documentation for PFS. ;)
(http://blog.lib.uiowa.edu/preservation/files/2011/01/closed.jpg)
(http://biggeststuff.com/wp-content/uploads/2013/02/worlds-longest-book.jpg)
Edit: Actually, no, this is my copy of "Understanding Women". :laughing:
-
:laughing:
-
Documentation for PFS. ;)
What? They speak Chinese in the Netherlands now? I thought it was English ;).
Edit: Actually, no, this is my copy of "Understanding Women". :laughing:
Isn't that a chapter from "The Art of Love and War" by Shi Sun Tzu Mi? It takes a lot of Chinese characters just to write, "I know nothing ... nothing at all".
-
Post a screenshot of your CD0: device settings (the text file)?
I had to work really late last night and couldn't get to my Miga, but I'll get this information tonight for sure. Thanks again for putting brain power into this Mike!
-
Post a screenshot of your CD0: device settings (the text file)?
Ok, here are the prefs Mike.
(http://www.danschallock.com/amiga/CDFS-pref.jpg)
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
Hiya buddy!
I mean the text file, it should look something like the last screenshot of post # 9 (http://www.amiga.org/forums/showpost.php?p=796168&postcount=9).
But on this one, why is yours CD1: instead of CD0:?
I'm still kind of grasping for straws here, but what I'm thinking is that maybe you have some kind of issue with the Mask or MaxTransfer value of your CD driver. I've never heard of this being a problem with a CD before, especially not with SCSI, but am sure you've heard how having the wrong values can affect A1200/A4000's - file corruption, etc. when trying to read large files. And I assume the video files on the CD that it's trying to validate against are pretty big...
Edit: any luck finding that adapter to put your CD drive on the warpscsi.device chain?
-
Hiya buddy!
I mean the text file, it should look something like the last screenshot of post # 9 (http://www.amiga.org/forums/showpost.php?p=796168&postcount=9).
But on this one, why is yours CD1: instead of CD0:?
I'm still kind of grasping for straws here, but what I'm thinking is that maybe you have some kind of issue with the Mask or MaxTransfer value of your CD driver. I've never heard of this being a problem with a CD before, especially not with SCSI, but am sure you've heard how having the wrong values can affect A1200/A4000's - file corruption, etc. when trying to read large files. And I assume the video files on the CD that it's trying to validate against are pretty big...
Edit: any luck finding that adapter to put your CD drive on the warpscsi.device chain?
When I installed 3.1 I used the CD0 device to get the CDROM working. When I was installing 3.9 I installed the CDROM software off the 3.9 CD and it automatically created CD1 because CD0 was already mounted. I just deleted CD0 after CD1 was installed. I'm not sure how many places I would need to change in order to switch it to CD0. Startup-sequence assign maybe and tooltype and rename the file?
Anyway, man I wish it was a max transfer thing. That would be a sweet fix.
Here is the text file I think you were talking about.
(http://www.danschallock.com/amiga/CDFS-prefs2.jpg)
-
This is an addendum to the logic in the previous post: You mentioned only having 2MB chip on the A3000 motherboard. The rest of your memory is on your accelerator. Your CD drive is on the A3000 built-in SCSI. Your hard drive is on your accelerator. Depending on what type of memory and how much is allocated to the buffer on the CD drive... I'm thinking it's trying to read these huge video files on the disc, and since it has to go through the motherboard to get from the CD to the accelerator memory, if it has to try to buffer through that meager 2MB of chip ram you've got on there... Get what I'm saying? Makes sense to my "it's 2am and I need to go the %#$# to sleep" brain, anyway. LOL. :D
-
This is an addendum to the logic in the previous post: You mentioned only having 2MB chip on the A3000 motherboard. The rest of your memory is on your accelerator. Your CD drive is on the A3000 built-in SCSI. Your hard drive is on your accelerator. Depending on what type of memory and how much is allocated to the buffer on the CD drive... I'm thinking it's trying to read these huge video files on the disc, and since it has to go through the motherboard to get from the CD to the accelerator memory, if it has to try to buffer through that meager 2MB of chip ram you've got on there... Get what I'm saying? Makes sense to my "it's 2am and I need to go the %#$# to sleep" brain, anyway. LOL. :D
Actually that's pretty brilliant, or I'm equally tired. I think the easiest fix try for that theory is to get the CDROM on the warpdevice as well.
(http://www.amiga.org//www.pinterest.com/pin/create/extension/)
-
Gah, I'm confused again. So are you installing a fresh 3.9? Or 3.9 on top of 3.1?
Also, from your screenshot, "BufMemType = 513". I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:
Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM
Try changing that field to a 1 and see what happens.
Next try changing your MaxTransfer to 0x1fe00.
Try increasing the number of buffers from 50 to say, 200.
Make these changes one-at-a-time, and note if anything changes. :)
-
I think the easiest fix try for that theory is to get the CDROM on the warpdevice as well.
Yes, but you need a little Hardware-Hack to get it working in the A3000 !
It is incompatible with the A3000's motherboard SCSI controller - replacing the A3000's SCSI chip to rev. 08 solves the problem.
And the device is called warpdrive.device
-
Gah, I'm confused again. So are you installing a fresh 3.9? Or 3.9 on top of 3.1?
I did do a fresh install, it wasn't over 3.1... however the emergency disk I created was made on a fresh 3.1 install which meant the CD driver was the 3.1 CD0 driver in Devs/dosdrivers/. That was necessary just to get the system to boot and recognize the CD to be able to install 3.9. But the 3.1 CDROM driver has problems not the least of which is the truncated file names, so I installed the CDROM software from the 3.9 install which is improved. Does that make sense or am I explaining it wonky?
Also, from your screenshot, "BufMemType = 513". I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:
Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM
Try changing that field to a 1 and see what happens.
Next try changing your MaxTransfer to 0x1fe00.
Try increasing the number of buffers from 50 to say, 200.
Make these changes one-at-a-time, and note if anything changes. :)
Awesome tips, Thank you. I will try these one at a time. I guess the test after each change is to try and install boingbag1.
-
Yes, but you need a little Hardware-Hack to get it working in the A3000 !
It is incompatible with the A3000's motherboard SCSI controller - replacing the A3000's SCSI chip to rev. 08 solves the problem.
And the device is called warpdrive.device
Hi Rotzloeffel, Thanks for the feedback. I understand what your saying and yes I know its warpdrive.device (I was being lazy and typing short hand). What I meant by attaching the cd to the warp chain was to plug it in to the end of the scsi chain I already have coming off the warpdrive.device now. And I know that does work as I used to have a cdrom attached to it. I am only using the amiga 3000 scsi.device for it now is because it is a an external drive with the 25 pin external plug and it was just easier for me to plug it directly into the back of the A3000 rather than hacking a port for the internal warp ribbon to end in an external 25 pin plug.
-
Gah, I'm confused again. So are you installing a fresh 3.9? Or 3.9 on top of 3.1?
Also, from your screenshot, "BufMemType = 513". I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:
Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM
Try changing that field to a 1 and see what happens.
Next try changing your MaxTransfer to 0x1fe00.
Try increasing the number of buffers from 50 to say, 200.
Make these changes one-at-a-time, and note if anything changes. :)
Well I tried these. Nothing stopped working but it did fix anything either. What program do you to burn Amiga stuff to disk? Also what cd rom software are you using on your Amiga?
-
Well I tried these. Nothing stopped working but it did fix anything either. What program do you to burn Amiga stuff to disk? Also what cd rom software are you using on your Amiga?
Well, crud. Gotta get that CD drive onto your WarpEngine SCSI chain and see if that makes any difference. :)
I use Nero "Multimedia Suite" 10, Nero 12, and even the Windows built-in CD burning software, all have written discs just fine and read them back on my Amiga. On the Amiga-side, I use the standard CD0: setup that comes with 3.9. Literally the only thing I have to change is from scsi.device to gvpscsi.device, and the device # to match the # on my chain.
I've used MakeCD (on the Amiga) in the past to burn CD's that I can read back on my PC, but that is some of the most un-user-friendly software I've ever seen. Like Windows 8, you might call it outright user-hostile. ;)
You don't happen to have a different CD drive you can try, do you?
-
Just an update. I moved the CDRom from the scsi.device to the warpdrive.device. Unfortunately it didn't allow me install the boingbags successfully (same errors as before), however it did seem to alleviate some of the read errors I was getting on the CD when extracting archives off CDs. It's a long shot, but I am hoping that maybe my 3.9 is a a flawed install even though it seems to be working fine, and that if I reinstalled from the CD now connected to the warpdrive it would solve my problems. Like I said, a long shot, but I am running out of ideas.
-
UPDATE 10-7-15
I obtained another copy of the 3.9 disk. (I assure you I own a real pink copy by the way). I wanted to rule out something amiss with my copy. I also now have the cdrom drive connected to the warpdrive.device instead of the 3000's scsi.device.
I have had complete success through boingbag2.
Here was my procedure.
1) format workbench -clean slate
2) install 3.1 fresh and mount CD0 to get access to the CDdrive.
3) insert new copy of 3.9 disk and create EBD (emergency boot disk)
4) reboot from boot disk
5) re-format workbench -clean slate
6) install 3.9
7) install 3.9 internet software
8) install 3.9 cdrom driver (to replace the 3.1 driver in DEVS)
9) reboot
10) insert a cd burned on a PC (using windows 10 normal burning) with the boingbag updates (1-4) already decompressed (using winrar).
11) copy boingbag1 folder to RAM:
12) swap CD for new 3.9 disk
13) install boingbag1
14) reboot
15) repeat step #10 through #14 with boingbag2
Everything in the above steps works 100% including using the ROM updates with my warpengine. No problems, no errors, everything good! :)
Thanks to everyone for the help and education that got to this point. I hope this thread helps others get at least this far in in the future should they run into similar problems.
********************
I did attempt (and succeed) moving beyond and installing the boingbag3&4 combo (which by the way does not require the 3.9 disk inserted). The install seems to work fine however on restart I get messed up colors on my screen and various commodities return errors on startup. I will continue to try and discern the nature of those problems but I am happy I succeeded through boingbag2 at this point with a stable system.