Forum Replies Created
-
Posts
-
Actively – no. But if you have a bug, that is consistently reproducing itself, please write a detailed description and I will fix it.
It seems like some antiviruses simply mark all UPX-compressed executables as suspicious.
I have done an experiment: compressed notepad.exe using UPX. According to VirusTotal, 7 of 42 antivirus programs treat this program as suspicious (http://www.virustotal.com/file-scan/report.html?id=8ecdc24105027e26069060173936d7202fd60bdab3eb62ca71af18730892566c-1288962310). Moreover, the unpacked Portable WinCDEmu triggers no antiviruses.What do you mean by “does not unmount”? What exactly happens?
My bet is that your player “forgets” to close some of the files on the image, so, closing the player before unmounting the image should help.It seems to me that modern antiviruses get closer and closer to the approach “every program that does not have a certificate bought from me is a virus”.
Are you using Portable WinCDEmu, or the normal WinCDEmu? Can you also tell when exactly does F-Secure pop up the alert and what is the exact error message text, so I could look it up in google?The driver binaries (SYS files) are signed (otherwise Windows won’t load them). The driver package is not WHQL-certified, so Windows pops up a message box.
WinCDEmu is either a simple yet free tool, that allows mounting data disc images, rather than an all-in-one solution, that supports all and everything.
There are plenty of free tools for creating disc images and re-implementing such functionality in WinCDEmu would be unreasonable. As for the audio tracks/mixed CD images, I would recommend using various free software for converting those tracks to WAV/etc. files, as supporting such images in WinCDEmu would not be simple.Do you have a NRG or similar image mistakingly renamed to IMG? This is what usually causes that type of error. Can you upload the faulty image somewhere and post the link, so I could investigate?
Disabled a flag that was supposed to turn off read-ahead caching for image file, but apparently caused the side effects instead. As 3.4 was released just 1 day ago (and nobody complained about the issue before), I just updated its installer.
This is the way Windows cache subsystem works. If you just read the image file sector-after-sector, Windows will use all free memory to cache its contents. However, if some program wants to allocate it and no other memory is available, this cache memory will be used just as the normal free memory, discarding the cache contents.
On the other hand, if the effect causes noticable program slowdown rather than just messing with Task Manager memory statistics, please describe it in more detail, so I will investigate.Upd: please download version 3.4 again, I’ve added a flag that should completely remove all cache-related effects.
