janbredenbeek wrote:I've not been able to reproduce the problem on Qemulator. What kind of medium was win3_ mapped to (Windows directory or MDV/WIN file)? Was it perhaps read-only?
The file that I was trying to load was always in a drive mapped to a Directory - and for sure not read-only. I can read and write to that file and directory from SuperBasic, Zip, ED etc.
i tested with QED in a drive mapped to a zip file and to a drive mapped to a directory - there was no difference.
I also performed the test using my boot file (which loads PE, Mouse, Turbo Toolkit, Dj Toolkit) - and also without any boot file, so QED was the only loaded program. Once again, there was no difference.
Derek_Stewart wrote:When you say the drives are mapped correctly, can you show the drive mapping or maybe upload the Q-Emulator config file here so that we can see what you have setup.
I use QEmulator for Windows (registered) - on Windows 10
This is QEmulator's config
Code: Select all