The Virtual CD support forum

Virtual CD 9 SCSI Controller loaded but has problems , code 41

Just purchased Virtual CD and I'm having all sorts of issues
but I'll start with something which is probably at the root of things I would think. Examining the device manager results in finding the SCSI driver loaded for Virtual CD but it has issues, note that I do not find any Virtual CD roms per se but that may be normal.

Here is the message given by Windows on the properties sheet for the Virtual CD driver.

"Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

Click Troubleshoot to start the troubleshooter for this device."

I tried upgrading the device manager but I was told that it already had the best match so I guess I must direct it somewhere.

What should I do? Do I uninstall/re-install? Do something with upgrading the device manager using a specific resource?

Another quick issue is opening is that in general any function I try to open takes a while.

PC specs:

Core2 Duo, 6600 chipset, 2.66 ghz
2 gig ram Corsair XMS dominators
3 sata drives
1 plextor CD
1 external CD via USB
WinXP service pack 2
Virtual CD 9 latest release

thanks in advance,

-Charles

Filter driver problem?

I found a quite interesting article dealing with such a problem that points to filter drivers: http://amazingtechs.com/index.php?showtopic=24518.
First of all please send us the diagnostics output (Toolbox -> Show diagnostics) if possible so that we can try to determine which filter driver may be the culprit.
If you cannot send us the diagnostics output you can remove the filter drivers as described in the KB article below.

BTW: If you enter your name and email address (which is not shown in public) you'll be automatically informed as soon as there is a new answer for your thread!

Removing filter drivers from the registry

Your diagnostics

Thank you for your diagnostics output - I kept it internal. There are three filter drivers listed:
c:\windows\system32\drivers\pxhelp20.sys - Px Engine Device Driver for Windows 2000/XP - Sonic Solutions - 3.0.56.0
c:\windows\system32\drivers\pwd_2k.sys - Win2000 Framework for Packet Write Driver - Sonic Solutions - 7.2.0.15
c:\windows\system32\drivers\pfc.sys - Padus(R) ASPI Shell - Padus, Inc. - 2.5.0.204

At first sight I cannot tell if one of these drivers may cause the problem. Thus I'd recommend to give it a try and remove the filter drivers as described in the KB article below.

Any report back is highly appreciated!

Removing filter drivers from the registry

Not there yet

Update:

just removed the Upper and lower filters then restarted the PC. The virtual cd device driver still shows :

[quote]Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

Click Troubleshoot to start the troubleshooter for this device.[/quote]

Trying to load "CD Managemt" but it eventually blows up stating that it can't load the VCD player.

What else can I do to help debug this?

thanks

Still in limbo

I also went ahead and tried re-installing Virtual CD but to the same result i.e. the driver shows up with the warning i.e. yellow exclamation mark, stating error code 41. I figured I try uninstalling the driver and re-installing it manually until I figured that the hardware wizard was not going to work for this.

Driver problem

Normally such a problem should be solved after deleting the upperfilters and lowerfilters entries. This is also described in the Microsoft KB article #314060.

I forwarded this issue to our developer. Well, unfortunately it can be any driver that prevents the installation of the Virtual CD SCSI controller... The most likely ones may be
C:\windows\system32\drivers\sptd.sys - ??? - ??? - ???
(Please the following link which may be applicable: http://www.disc-tools.com/download/sptdbeta)
C:\windows\system32\drivers\cdudf_xp.sys - CD-UDF NT Filesystem Driver - Sonic Solutions - 7.2.0.15
C:\windows\system32\drivers\cinemsup.sys - SW CineMaster Support - Sonic Solutions - 1.0.1.14
C:\windows\system32\drivers\dvd_2k.sys - DVD-RAM AddOn Driver - Sonic Solutions - 7.2.0.15
C:\windows\system32\drivers\dvdvrrdr_xp.sys - DVDVR Filesystem Reader Driver - Windows (R) 2000 DDK provider - 7.2.0.15

Which kinds of burning software or software which is able to burn CDs do you have installed?

Any report back would be highly appreciated!

CD burning installed software

MY PC is dedicated to audio and video production.

MediaMonkey -- installed after I noticed the issue with VCD 9
Adobe Audition -- hard disk recording software
WinAmp
Acid Music Studio -- hard disk recording studio
Roxio Easy Media Creator Basic DVD Home
Plextor Tools
Burrrn

I'll check out the links below. Mind you I don't think I have some sort of strange setup.

Speak soon.

PlexTools?

Either Roxio Easy Media Creator Basic DVD Home or Plextor Tools or Burrrn may be the cause for the code 41. I just can guess which software causes this problem, but I'd thing most likely it is PlexTools.

Any report back on this issue would be highly appreciated!

Plextools is what the pros use

To not use Plextools would be very unfortunate. I'll try getting rid of Roxio and Burrrn first.

BTW, the following:

C:\windows\system32\drivers\sptd.sys - ??? - ??? - ???

is apparently what gets installed when one installs Daemon Tools , something which I had actually installed prior to Virtual CD but had as well uninstalled prior to installing Virtual CD. Obviously, the uninstall did not get rid of the file. After some research, I updated the file to the latest version , uninstalled Virtual CD and reinstalled it again.

Unfortunately , still have the same problem.

PlexTools

Well, my last experience with PlexTools is several years ago - and I must say they were quite useless at that time...

Anyway, just let me know if removing any of the "suspicious" programs solves the problem!

Should I re-install

So after I uninstall one of these possibly offending programs should I re-install Virtual CD ? Or should just uninstalling the program be enough?

thanks

Could not set scsi security , ErrCode: 2

First of all, I uninstalled Roxie, Plextor and Burrrn and re-installed VCD 9. I still get the same error code 41.

I also noticed that if one inspects the properties for the driver that it shows the "resource" as not being set. It is apparently possible to set the resource to a user specified address area. Is this advisable?

Finally, I thought i check the event log just in case and sure enough I found both error and information events:

Info:
Mismatch in drives number found in regkey(1) and system(0)
Error:
"Could not set scsi security, ErrCode: 2"
Error:
"OpenFileMapping _VCD_V9_MemSection_ failed, 2"

Resource

You wrote: "I also noticed that if one inspects the properties for the driver that it shows the "resource" as not being set. It is apparently possible to set the resource to a user specified address area. Is this advisable?"

As we have no idea at the moment what may cause this problem in your case this may be worth a try...

Let me ask this again

What is the significance of the error I show from the WinXP event log for VC9 i.e. the same errors that show up in your diagnostics :

Info:
Mismatch in drives number found in regkey(1) and system(0)
Error:
"Could not set scsi security, ErrCode: 2"
Error:
"OpenFileMapping _VCD_V9_MemSection_ failed, 2"

Can you pls confirm that in a properly installed VC9 driver that there is actually an allocation for memory range, i/o range and irq? I feel very nervous about doing this manually. Messing with these type of settings is just the type of thing that would hang one's PC. Really , something that an installer should do programatically since it has access to info that a human being may not readily have.

Finally, I have seen posts from you where you suggest for similar although not exact issues that the VC9 "controller" be started manually for which you show some example command prompt code. Is the "controller" the driver, should I perhaps try that first?

Do you not have other diagnostic tools that you can provide.

I once had an issue with a vendor of another application which was difficult to debug. They actually went to the trouble of providing me with with a "debug" version of their application in order to get to the bottom of the issue and we were successful. Can we perhaps do that? Also perhaps it is useful to mention that I am a professional programmer and therefore may have the skills to undertake some QA tasks here i.e. given that you provide me with some tools or debug version of your app. I of course do not mean anything that would expose your code.

Please realize that I unfortunately already paid for your product i.e as you well know and that I encountered the issues immediately. I am not just testing out the trial version , something which I should have done prior to purchasing . I have already spent 4 evenings for which I have stopped doing work on our project to handle this issue.

I have btw, also checked the PC for viruses and it is clean.

thank you for your time,

-Charles

less than ideal solution

I have been somewhat successful in that I gave up trying to install VC9 on my new Core2 Duo system but instead I installed it on my notebook which is at least 3 years old, a Pentium IV 3.2 ghz on WinXP service pack 2. The notebook comes with one CD RW, it has a ton of CD burning apps and other multimedia apps.

VC9 installed quickly and fine and I was able to burn to the virtual burner. So it seems to me that the issue may be more related to newer hardware and bios.

This solution unfortunately is less than ideal and actually probably not viable for me. My objectives is to be able to quickly burn both CD and DVD and quickly be able to evaluate the end result which is why the notion of a virtual DVD/CD rom is perfect and something that would greatly facilitate my workflow. My pro audio/video apps are on my main PC i.e. not on the notebook, therefore its imperative that I be able to burn from my main PC somehow but unfortunately so far I am only able to install VC9 on my notebook.

OpenFileMapping _VCD_V9_MemSection_ failed, 2

This error message is related to the problem that the Virtual CD SCSI controller is not installed properly. The driver and the Virtual CD Player communicate over a so-called shared memory (as the driver cannot contact the player directly).

I doubt that the problem is related to the newer hardware of your PC (but I don't say that it is not possible). Most likely it is a driver conflict. I'm quite sure that Virtual CD will install without any problem on your PC with a freshly installed OS. Unfortunately we have no idea which driver may cause the conflict just by looking at the diagnostics... :-(

Normally the ressources of the Virtual CD SCSI controller are configured automatically, but you can try to change the ressources if they show a conflict.

Any report back is higly appreciated!

No conflicts are shown

there are no conflict shown as far as to memory address range, irq and so forth. Its just that the installed VC9 driver does not have any of these configured to any value.

Again, I have a lot more stuff loaded on the notebook. If there was a systematic way of turning a potential driver off I would do it, I would be more than glad to turn them all off i.e. cd-rom related drivers, but re-installing my OS is not viable and should not be a pre-requisite to the installation of any app.

Nothing configured

Hm, I'm not quite sure if I relally understand what you mean with that the "VC9 driver does not have any of these configured to any value". Could you please send me a screenshot to vcdtechsupport@hh-software.com.

Thanks!

Your screenshots

Thank you for your screenshots, Charles! Actually the resource type is not set! The default value is FFFF - FFFF. Maybe this I/O range is occupied by another device. Please try another free range.

Regards,

Harmut said:

"Thank you for your screenshots, Charles! Actually the resource type is not set! The default value is FFFF - FFFF. Maybe this I/O range is occupied by another device. Please try another free range."

well, yes , that is what I mean, which is why I had previously asked if I should try to manually configure these, it makes me nervous but I'll try it i.e. for now specifically the i/o range.

I tried but to no aval

I was able to manually configure the i/o range but still the VCD 9 driver is reported as bad

sent pics to support

Resources

Well, I guess that this is not a resources problem anyway. You can set the resources to any I/O range as we don't really use this, but just set it to "satisfy" the system...

Unfortunately I have no idea anymore. I even doubt that remote support will help to find out which driver is conflicting here. This is what Microsoft suggests: http://support.microsoft.com/kb/310123/en. I think we tried all possible solutions besides reinstalling Windows XP...

But I can't follow MS recommendations with VCD 9

Unfortunately for me I can't follow MS recommendations in the case of your product since VCD 9 would fall under the category of a "non-plug and play" device. Therefore I would need to be able to go thru the hardware wizard but I am not able for one to add the driver manually since its stuck in your cab files then therefore the only other choice is to let MS look for the driver and it returns by complaining that it could not find any other driver but the one already installed and therefore does nothing.

Again, there is a vulnerability in your application. You are supposed to be doing a "complete" job of emulating hardware and you simply have not covered all of your bases. My gut feeling is that you do have certain issues with newer type hardware and perhaps BIOS. BTW, can my SCSI bios settings in anyway affect your application ?

Here is Microsoft's recommendations:

Code 41
Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)


Recommended resolution


A driver was loaded but Windows cannot find the device. This error occurs when Windows does not detect a non-Plug and Play device.

If the device was removed, uninstall the driver, install the device, and then click Scan for hardware changes to reinstall the driver. If the hardware was not removed, obtain a new or updated driver for the device.

If the device is a non-Plug and Play device, a newer version of the driver might be needed. To install non-Plug and Play devices, use the Add Hardware wizard. Click Performance and Maintenance on Control Panel, click System, and on the Hardware tab, click Add Hardware Wizard.

On the General Properties tab of the device, click Troubleshoot to start the Troubleshooting Wizard.

Driver problem

The Virtual CD driver is certified by Microsoft which means that it has been tested very carefully. Of cause we cannot completely eliminate the risk of incompatibilities with other (SCSI) drivers. I can imagine that your SCSI bios settings may affect Virtual CD.

The manual installation of the Virtual CD SCSI Controller can be done as follows:

• Please remove the SCSI Controller from the Device Manager and reboot.
• Then go through the Hardware Wizard to install it again. The required INF file is a OemXX.inf in C:\WINDOWS\inf (the inf folder may be hidden). XX stands for any number (normally the highest one), the first line in the inf file is ";vdrv9000.INF -- This file contains description for Virtual CD driver".

If you encounter any problem during the installation of the driver please read the KB articles below.

Cannot create virtual CD drives.

The drivers for virtual drives cannot be found during the installation of Virtual CD.