View Single Post
Old 31 August 2016, 18:10   #141
Registered User

Join Date: Mar 2016
Location: Gothenburg / Sweden
Posts: 23
Originally Posted by Toni Wilen View Post
It is not normal and it is already fixed. Including lots of edge cases if "weird" or "too much" RAM is enabled where wrong mode was selected causing possible crashes.

Ok, it could be scsi emulation related (nothing done there but side-effects are possible). Put hdf back in CSPPC scsi, run winuae with -log -scsiemulog command line parameters with only one drive mounted (in CSPPC SCSI unit that since 3.4 fails to detect anything), wait until KS boot screen appears (and no drive detected), quit, attach winuaelog.txt.
Hi. Dont know if i did it right, had to google a bit on commandline but here is what i typed in cmd on windows10. In the config i use only the controller Accelerator (Cyberstorm PPC) unit1. Partition only Work (DH1, not bootable). The screen goes black and nothing comes up. Its just waits forever. No kickstart logo or anything.

winuae64.exe -f Configurations\OS4.1FEtest.uae -log -scsiemulog
Attached Files
File Type: txt winuaeCMD.txt (28.5 KB, 55 views)
File Type: txt winuaebootlog.txt (12.8 KB, 47 views)
psykicko is offline  
AdSense AdSense  
Page generated in 0.05724 seconds with 10 queries