Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: curtis on August 01, 2016, 08:55:56 PM
-
Okay, thought I'd start a new thread to keep the other things driving me buggy separate!
I have an A500 with 2MB chip, 8MB fast, and 2MB 32 bit RAM.
Mega Midget Racer 68030 clocking at 33MHz.
I have an original 3.9 CD that I bought.
3.1 currently installed and everything is running smoothly.
CD is recognized and OS 3.9 CD is recognized.
However, when I try to install 3.9 clicking on the installer nothing happens.
Tried a couple of variations clicking on the "Install OS 3.9) tool and clicking on the Installer. NADA.
When I click on the 3.9 tool I get an error saying script cannot be run or found.
I have noticed I do not have the typical icon for the install 3.9. Rather I get the "hammerhead" tool icon. Ditto on the installer icon.
I downloaded another copy of 3.9 I found online and burned it to CD and tried it. Same result.
I'm open to suggestions.
I do have Amiga Forever Plus edition so am thinking I should try an install using that.
Suggestions? Please!
-
IMHO if you want to install 3.9 the best way to do it is by making the ERD (Emergency Recovery Disk) and booting off that. Then create a new partition, or install a new device (for example, pop in a new CF card) and install on that. By installing fresh you can avoid any problems of old, legacy files being left behind to muck up the system. The tool to create an ERD is on the 3.9 CD.
I cannot stress that enough, for the same reason that any time I'm building a PC I do a fresh install of the OS and all core applications, rather than an upgrade on top of an existing OS. In the long run it'll make your life a lot easier when it comes to tracking down strange bugs. ;)
That being said, I popped in my 3.9 disk and the 3.9 installer is a "Project" icon. Are you sure you're clicking on the right thing? A couple different icons should come up when you insert the CD. See attached screenshots:
-
Side note, check out the typo in my second screenshot, above. :lol:
-
I'm still working on my develpoment!
An update.
First, can't create the emergency boot disk. Same thing as the install routine. Just a "hammerhead" icon.
Got Amiga Forever fired up and added the CD and an IDE CF card.
Surprisingly enough, I get the proper icons!
Went through the process and it APPEARS to have installed 3.9 on the CF card.
Edited the startup-sequence to include the CSA-MMR configuration sequence in the first line. Will now try it in my 500.
Stand by...
-
And no joy.
All I get is the animation asking for a 3.1 boot disk.
Taking a break for the day as I'm getting a headache!
-
BTW, would LOVE to hear from ANYBODY who has successfully installed 3.9 in a similar configuration!
-
Did you look at my screenshots? What, exactly, are you seeing when you open the 3.9 CD? Post a picture. Do you see icons, like in my screenshot, or just the generic "tool" icon? (hammerhead)
This isn't exactly rocket science, double-clicking on the "OS3.9-Installation" icon should launch the installer. It almost sounds to me like your system isn't reading the CD correctly. I'd go back and re-visit that. If you're not seeing the proper icons, then your system isn't reading the CD correctly. Probably a file system issue, you need to get that addressed first.
-
He's running into the install from 3.1 and the installer from 3.9 problem..
as well as other issues
-
And no joy.
All I get is the animation asking for a 3.1 boot disk.
Taking a break for the day as I'm getting a headache!
Sounds like your CF card isn't bootable. Load HDToolbox and check that the CF partition on which your OS3.9 installation resides is set to be automatically mounted and bootable.
-
Did you look at my screenshots? What, exactly, are you seeing when you open the 3.9 CD? Post a picture. Do you see icons, like in my screenshot, or just the generic "tool" icon? (hammerhead)
...Probably a file system issue, you need to get that addressed first.
+1
-
Agreed, sounds like a CDFS problem. Which one are you using?
-
Okay, here we go.
CDFS I'm using is from aminet. atapi_pnp300 which was recommended as a get by until I could get 3.9 installed.
First picture is what loads up.
Second picture is what I'm seeing when I open the Emergency Disk folder.
Third pic is 3.9 Install Tools folder.
Fourth is 3.9 Installer folder
And fifth picture is all I ever get when running the OS3.9_install program, or actually anything on the 3.9 Cd.
Next post will get the rest of the pics.
-
Okay, continuing:
When I open the 3.9 CD and set it to show all files, I get pic #1.
Second picture is when I click on the CD tool under WBStartup folder
Last but not least, my current config.
-
You shouldn't need to set it to "show all files". It should have icons (.info files) just like any normal Amiga disk, that you can execute the installer from. That's your problem. There's either something wrong with your disc, or with your file system. I'm going with "file system", and would suggest first trying the one that comes with 3.1. It's kinda rubbish, but should at least be able to read a normal Amiga CD, haha. ;)
-
Fourth is 3.9 Installer folder
Also, this is the wrong location. The correct path is highlighted in my earlier screenshot. Open CD --> Open folder "OS-Version3.9" --> Double-click on the installation icon "OS3.9-Installation"
-
This is my 1. gen OS 3.9 disk. You are missing the Project icon (OS3.9install.info). Try to
-
When I try to run the OS3.9install, I get the execution failed error.
This is my 1. gen OS 3.9 disk. You are missing the Project icon (OS3.9install.info). Try to
-
OH, forgot to mention when I run the CD under Amiga Forever emulator, it works.
So, it really does sound like the CDFS is wonked.
Will try the OS 3.1 CDFS and see what happens.
-
OH, forgot to mention when I run the CD under Amiga Forever emulator, it works.
So, it really does sound like the CDFS is wonked.
Will try the OS 3.1 CDFS and see what happens.
Thought you would have tried the filesystem first, as there really is nothing else it could be other than a virus that hides .info files.
Alternatively, you could run the Installer command with the installation script file as its argument (as a last resort).
-
I used AmiCDFS for a number of years so with no problems so you could download that from Aminet and give it a try.
-
I think I will try a new CF and a full, new load of 3.1 then try 3.9 and see what that gets me.
-
AsimCDFS is what I always use, never fails to do it for me whether it's my A2000 or 4000T.
-
I think I will try a new CF and a full, new load of 3.1 then try 3.9 and see what that gets me.
Load 3.1. Use it to create the 3.9 ERD. Then boot off that and wipe everything, start fresh.
On the bright side, the CDFS stuff that comes with 3.9 works a lot better, out of the box, than what comes with 3.1. Not that that helps you very much right now, lol. ;)
-
installed 3.5 ..it just worked ....have you tried updating the installer ..i found my icons went south a few times when ever i did a 3.5 update on 3.1 ..re installed to latest version installer and problems went away ..
-
Just finished a fresh 3.1 install.
Tried the CD0: and it SAYS it mounted the Cd, but I can't get to it. Tried changing the unit number from 2 to 1 and that didn't make any difference either.
@AAACHIPSET. Are you talking about the installer that comes with 3.5/3.9? If so, where did you get it?
Anyway, I'm going to backshelf this for now as I'm getting ready for the VCF this weekend. Need to pack and all that stuff.
Will start fresh on this Tuesday.
-
You problem's not the installer, it's with the CDFS, or with your SCSI config.
But if you want it, the updated 3.1 installer is here: http://aminet.net/package/util/misc/Installer-43_3
-
With your old install, I belive you were very close to success. Because you obviously was able to browse the OS3.9 CD, and maybe it was possible to copy files from it as well. Then you could have copied the CacheCDFS file from "Emergency-Boot/L" to the L dir on your boot partition, and then copy CD0 from "Emergency-Boot/Storage/DOSDrivers" to Storage/DOSDrivers as well (making sure that it didn't overwrite any existing file). Now it only would have been a matter of editing the CDO file, where the Unit and Device lines got their correct values. Since you were using atapi_pnp300, I will guess either cd.device or cd_a600.device for the latter.
Then you could have used this CD0 file for mounting your CD-ROM drive instead.
With your new install, the main problem is that you cannot use scsi.device as Device in the CD0 file. This is because scsi.device in KS3.1 and lower doesn't support CD-ROM drives (which is what stuff like atapi_pnp300 fixes). Another thing is that the standard CDFileSystem only supports ISO9660, which in turn means that file names will be shortened to eight characters.