Search

All words One of these words Exact wording/phrase

10 - 25 - 50 Hits per page

Short version Long version

---

Tags VirtualCD.V9 VirtualCD.V8 VirtualCD.V7 VirtualCD.V6 VirtualCD.V5 VirtualCD.V4 VirtualCD.V10 VirtualCD.Known Problems.V9.Unfixed VirtualCD.Known Problems.V8.Unfixed VirtualCD.Known Problems.V7.Unfixed VirtualCD.Known Problems.V6.Unfixed VirtualCD.Known Problems.V5.Unfixed VirtualCD.Known Problems.V4.Unfixed VirtualCD.Known Problems.V10.Unfixed

After a reboot inserted virtual CDs are no longer in the virtual drive.

Although the option "Eject when the session is ended" in the Image File Properties is not set, the virtual CDs are ejected after a reboot.

Please be aware that virtual CDs which are inserted in a physical drive are always ejected on shutdown to avoid problems with the physical drive (s. KB article #2137).

If you are using Virtual CD version v6 or v7 (up to v7.0.x) under Windows 98/ME, please read this KB-article: Virtual CDs not inserted after a reboot under Windows 98/ME

At the end of a session, Virtual CD v4 writes "Unit_0 = C:\Images\Image.vc4" in the Registry key "HKEY_LOCAL_MACHINE\SOFTWARE\H+H ZfRk\Virtual CD 4" for each CD that is in a virtual drive (unless the "Eject on exit" flag is set). Any existing entries of this type are deleted before this value is written.

Please note that the information about inserted virtual CDs is stored separately for each user for Virtual CD v5 or higher! The corresponding value is "Drive_" (e.g. Drive_D for the virtual drive D:) in HKEY_CURRENT_USER\Software\H+H Software GmbH\Virtual CD 5 etc.

If an inserted CD is no longer in its virtual drive after the system is restarted, the error might be caused by one of the following:

• The session was not ended correctly (e.g. because the computer was simply switched off).
• The virtual CD was no longer available once the session ended (e.g. because the network connection was deactivated).

In either of these cases, the required registry entry was not saved, or was not stored correctly.

Another possible cause of the error might occur when the computer is restarted; when the system is started, the VCD driver reads these Registry entries and tries to insert the corresponding virtual CDs. In this case, the error might be due to one of the following:

• There are no registry entries (see above for details).
• The virtual CD is password-protected. Since the password is not stored with the virtual CD, the driver cannot insert it.
• The driver cannot access the virtual CD (e.g. no access permissions, no network connection).

Solutions and Workaround:

For larger installations it is worthwhile to use Virtual CD NMS, the Management Software for Virtual CD. In addition to the license distribution NMS offers you a completely management via profiles. For instance, you can also allot virtual CDs and block drives, so that the virtual CDs cannot be ejected.

Workarounds:

1. Enter a start program in the Image File Properties (CD Management).
2. Create a shortcut via the Image File Properties (until version 5) resp. the context menu of the virtual CD (version 6 and higher).
3. If needed move the shortcut to Start\Programs and replace the existing one or to the autostart folder to automatically insert the CDs after login.

By executing the shortcut the virtual CD will be inserted and the program executed in one step.

Alternatively it is possible to use VBScripts as of Virtual CD v5. Please read the manual for further advice!

As of Virtual CD v9 you can create a snapshot of your inserted virtual CDs which then can be reloaded easily with a click.

---