Forum Replies Created
-
Posts
-
Appreciate the help, but unfortunately this isn’t working in my case…
After disabling Driver Signature Enforcement on bootup, the same thing happens:
When I install the app, I chose YES at testsigning but then it only gives me the choice of restarting the computer – no files are written, so I can’t continue with step 3 (the WinCDEmu folder doesn’t exist).
I knew it.
This 2nd impression.
viewtopic.php?f=3&t=117#p1631. You need press F8 key whilst boots and selecting the “Disable Driver Signature Enforcement” boot option just for install.
2. Install WinCDEmu 2.3 to the WIn7 64Bit, and press YES button when testsigning mode window.
3. Copy C:Program FilesWinCDEmux64*.sys to C:WINNTSystem32drivers.
4. ReBOOT your computer, then WinCDEmu will run with no F8 key.SystemStartOptions:
TESTSIGNING NOEXECUTE=OPTINBCDEDIT says the operation completed successfully when enabling manually
Installed beautifully, but on first run while opening an ISO I got an error message indicating there was a missing driver. When I clicked “Update Driver” it seemed to skip the update process and went on to mount my ISO perfectly. The missing driver error has not occurred since then.
Awesome program, guys! I’d say “flawless” but that’s just darn hard to achieve. 🙂
Installer fail at checking TESTSIGNING ON when installing on Windows 7 RC 64Bit environment, then it will loop infinity .
but no *2.For future versions support for MDS/MDF and NRG images would be nice.
Thanks for this very usefull utility.
Heinz
@bazis wrote:
The GUI will still be simple and will not cancel the simplicity of single-click mounting. You’ll be able to choose whether to prompt for a drive letter on each mounting, or use the default one.
I’m not sure if this is what I like to see *g*
Atm we have this behaviour of WinCDEmu:
When an image is mounted WinCDEmu reserves the first free drive letter (a: and b: are not choosen if there is no floppy drive).
So when you have 3 Partitions and one DVD-Rom you have letters C:, D:, E: and F: reserved and the first image would take the G: letter.
Every additional image would tage the next free letter etc.What I’d like to have:
The old behaviour should be the standard for every user. Plus we get an option to set a new “starting drive letter”. E.g. I like to mount my images to the
driveletter V: (like “V”irtual). So the first mounted image get’s the V: and every additional image W:, X:, etc.I hope that makes it a bit more clearer 🙂
Regards,
HighendHi,
He has digitalsign personaly.
http://crystalmark.info/information/vista-e.htmlI do not like tricky one. Simpl is better. Light is better. No GUI necessary. Just doblue click ISO.
I JUST want both drivers next time which is JUST digital signed.Regards,
This is a great piece of software and will be my light weight replacement for D-Tools – continue the good work.
@bazis wrote:
When WinCDEmu is first installed, it sets up the driver for the virtual disk bus. As no virtual drives are present at that moment, the driver is not installed. This will maybe[/i/ be fixed in further versions by flushing an empty virtual drive during installation and updating the drivers.
Ok, thanks for the explanation. I hope it’s more than a “maybe” *g*
Drive letter selection is a little bit tricky, however, I have an idea to implement something similar in the next version. However, note that the driver letter cannot be reserved while virtual CD is not active (if you insert a USB FLASH disk, it can still ocupy the letter), however, it will be possible to assign a given letter to a newly mounted image, instead of default one.
It wouldn’t matter that it is not possible to reverse it while the virtual CD is not active as long as we can define a default letter (and that will vanish like now when the CD is unmounted).
If you need somebody to test these changes just tell me in this thread (if you like).
Thanks for listening to the users regarding changes / feature requests!
Regards,
HighendThank’s,
This time it gave to me a pure blue screen. 😀
DependencyWolker said no error.
And blue screen said,
*** STOP : 0x000000D1 (0x07CB4000, 0x00000002, 0x00000000, 0xF5C80D64)
DRIVER_IRQL_LESS_OR_EQUAL
*** Address F5C00D64 base at F5C80000, DateStamp 3d90d765 – Cdr4_2K.SYSThank’s,
But it did’t work.
DependencyWolker said “No PE signature found. This file appears to be a 16-bit DOS module.” and “Error: At least one file was not a 32-bit or 64-bit Windows module.”
