WinUAE questions and problems! NEED HELP FROM EMULATION GURUS!

[Glaucus]

Well, WinUAE can be tricky to diagnose.  However I would try using a vanilla AmigaOS3.9 bootfile.  From your description of your setup it sounds as if the AmigaOS files are in a FAT32/NTFS folder?  Try using a harddisk file instead.  For my setup I placed all the AmigaOS specific files on a dedicated HD file.  All my apps and data however are stuffed in a regular FAT32/NTFS folder so I can access them with Explorer, etc.   I have found that there are cases where certain file names or file locks can cause problems when you are accessing a native Windows filesystem.

Aside from that I'm not sure what else to say.  I can say that my setup has the CPU set to 68040, CPU emulation speed set to Fastest Possible, 8MB JIT cache, Const Jump, FPU support, Force Settings, No Flags and Indirect are all checked.  It works fine for me.

I've also found that some badly behaved Amiga software can cause WinUAE to crash.  Make sure you're not running any hacks.  It's possible that AWeb causes problems, although my registered version works fine under WinUAE.  There's also a "winuaeenforcer" that you run and it might help you find any misbehaving software.  Anyway, good luck!

  - Mike

[Glaucus]

Hey, well guess what!  I just tried it and AWeb crashed when I went to Amiga.org. I even had winuaeenforcer running and it gave me a nice little report, so I'm pretty sure it's AWeb's fault, not WInUAE.  Of course this doesn't help much but if you're really serious about fixing this you might wanna dissect Amiga.org's HTML and perhaps suggest a fix to wayne?!? (although really it's AWeb that should be making the fix).  I'm assuming Amiga.org's main page has some new HTML code that causes confussion in AWeb and it just blows up.

  - Mike

[Glaucus]

I have found that there are cases where certain file names or file locks can cause problems when you are accessing a native Windows filesystem.

Umm.. Sounds like my problem with Payback

Yeah, just to back that up a bit...  I have actually emailed the current developer of WinUAE about some filesystem bugs that I discovered a while back.  Shared file locks on files that reside on a Windows native FS have caused problems in the past.  The latest version does seem to fix them but there could still be some more unknown FS problems.  Also worth noting is that the standard Amiga FS allows some characters in filenames that are not allowed in FAT32/NTFS.  I've found that if you attempt to create a file with these particular characters WinUAE will attempt to create them and end up locking itself up in the process.  I first discovered this when I attempted to copy over my entire Amiga4000's HD into an NTFS filesystem so I could then back it up onto CD-ROM.  The system kept crashing on me until I realized this little problem and renamed the guilty files on the Amiga before transferring them.  Just something to keep in mind.

  - Mike