Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Tumbleweed on August 04, 2021, 06:10:00 PM
-
Hi all,
Since upgrading to OS3.2 from OS3.9 none of my WHDload installs work - boot to either a black screen or a flickering screen with corrupted graphics.
WHDLoad is the latest version from whdload.de and the installs / slaves are the latest versions
Ive played around with tool types - nommu, nocache etc increasing stack size but no joy. Ive tried booting with cache disabled from the OS3.2 boot menu (I have 3.2 Roms) but no luck either.
I have a500 kick rom in devs/kickstarts along with the RTB file. All worked mostly ok with 3.9 but what was working now isnt.
Amiga is a A3000T, Kick3.2, OS3.2, CSMKII 060 128MB Ram; Cybervision64.
Any ideas? any help greatly appreciated.
Weed.
-
I have OS3.9 all my machines, even when I own several copies of OS3.1.4.
So reupgrade back to OS3.9
-
So go back to OS3.9. Does 3.9 work with 3.2 ROMs?
-
maybe you could try a fresh install of AOS3.2 as it is the recommended way of installing it !
mixing AOS3.9 components with AOS3.2 might be the culprit...
-
I only had an issue with one game, F1GP, after I upgraded to 3.2 but it might be unrelated. It would start the game with one of the in-game screens showing but go to a black screen; the game usually starts with a grey/black AmigaDOS 1.3 screen first. I redownloaded the slave and it was ok.
-
maybe you could try a fresh install of AOS3.2 as it is the recommended way of installing it !
mixing AOS3.9 components with AOS3.2 might be the culprit...
In the manual for 3.2 it says you can install 3.2 over 3.9 - just miss out a few of the early steps. Maybe because I've tweaked my OS3.9 installation BB3 & 4, icon.library and a few others its causing problems with WHDLoad.
I now have it working.
I created a new partition. Clean installed 3.2, installed Picasso96 and then WHDLoad. All working fine. I now have two boot partitions one for my OS3.2/3.9 and the new clean OS3.2. I can then select which one to boot into from the OS3.2 boot menu.
I'd rather just have one boot partition but for mow its a decent workaround.
Thanks for your help.
Weed.
-
After a bit more digging it looks like the issue may be with network. I installed Roadshow, then SMBFS Mount and SAMBA and now I am experiencing the same issues as before with my original install.
More investigation ....
-
Disabling Roadshow by commenting out the startup lines in user-startup fixes the problem.
My initial question OS3.2 & WHDLoad now looks to be misguided - should have been WHDLoad & Roadshow.
-
Doesnt look like its an issue with Roadshow. I downloaded MiamiDX off Aminet and installed it. When on-line WHDLoad games dont load. When off-line they work fine.
Ive tried changing tooltypes on the WHDLoad slave's - added NoNetwork but didnt make any difference.
Im missing something but for the life of me cant seem to find it!
Any one got any ideas?
Best.
Weed
-
Hi Tumbleweed!
Unfortunately, that's a known "bug" in WHDLoad, check this discussion (http://eab.abime.net/showthread.php?p=1332343&postcount=9). It doesn't (seem to) matter if you use Miami (like me) or Roadshow.
I don't know if work has been done on it but I still have this problem with the latest WHDLoad (yes, the one that can use the network ;D).
Take care!
-
Interesting that Genesis / AMITCP is only TCP/IP stack wich works fine with WHDLoad.
-
This is a solved problem. There are settings in the prefs file for what scripts to run before slave is loaded and after slave has quit, the example scripts already have shutdown/restart methods for Miami and Roadshow. Look in files S:WHDLoad#?
-
Thanks all. I spent a few hrs on it today. Ill have another go tomorrow.
Weed
-
There is a discussion on eab, about this seems that Roadshow has some problems with WHDLoad
The issue with Roadshow is that it does not support "offline". When you switch Genesis to offline, it is still running, just does not have a network connection.
The only way to stop Roadshow from having network connections is to shut it down completely. But a TCP/IP stack cannot be shut down if programs are still using TCP/IP. That's especially bad if you use something like SMBFS because SMBFS cannot shut down if some files or directories on the network share are still open.
-
Cheers Utri. I have a SMBFS share running so I guess that comlicates things. What I did manage to ascertain this afternoon using my clean OS3.2 install with Roadshow and SMBFS Mounter was that I needed to unmount the SMBFS share then issue the NetShutdown command. Probelme is NetShutdown isnt perfect and doesnt always work (known problem and is documented in the Roadshow docs).
I plan to congigure thre start-up and clean up scripts and see how that goes.
If I have no joy with it I still have it working on my clean OS3.2 partition which isnt network enabled automtaically. Ive set Miami to only start manually. Same with the SMBFS. Works perfect been playing Battelsquadron, Rainbow Islands, RikDangerous all work perfectly.
Weed
-
This is a solved problem. There are settings in the prefs file for what scripts to run before slave is loaded and after slave has quit, the example scripts already have shutdown/restart methods for Miami and Roadshow. Look in files S:WHDLoad#?
Thanks Kolla - I edited the WHDLoad startup scripts in s: uncommenting the entries for roadshow and SMBFS. At first it didn't work. Machine froze when I clicked any WHDLoad slave icon. Reboot. Then opened a shell and entered netshutdown. Machine froze.
Reboot.
I then went through my user-startup commenting out everything other than roadshow, MUI.
Reboot.
Opened a shell and entered netshutdown. Success.
Then edited s:User-startup and added back what I had commented out. One entry at a time followed by a reboot.
All fine until I uncommented the entries for VNC and stringsnip. Netshutdown froze. Leaving them commented out WHDLOad is working as I wanted it. All ok.
Weed.