going from Beta to worse...

[aurfalien]

... so I installed RC1 the other day which is where my CDROM woes seem to have started.

I uninstall VMWare tool and try to re install it but just realized that I guess you need a CDROM for it to work.

Now why my CDROM dispeared is a mystery but the vmx file is in order according to other posts of other vmx files. The problem fist occured when I decided to give CDROM access back to OSX as I didn't feel like shutting down my VM.

There ar also serveral posts of probems like mine w/o resolve.

I did buy the product at the promo 1/2 price and I'm sure things will get beter but until then...

Is "any" one having issues like mine or am I a doof?

RC1 looks like is sux a$#.

[rhind]

I've got RC1 running on 2 machines (XP guests) and haven't had any issues like this. Could you try copying the hard-disk image out of the VM package, and re-creating the VM, then putting the hard-disk image back?

Cheers

Russell

[admin]

I don't know of changes to the CD code between beta 4 and RC1, nor do I know about the several other posts of problems you mentioned. Your other post didn't say exactly how CD-ROM access is not working for you, but I'd expect that VMware Tools installation would still work. What happens when you try to install VMware Tools?

[aurfalien]

Hi Magi,

This post ties into my other post.

In my guest OS (XP), I no longer have a drive letter for the CD/DVD. And when I place a CD into my drive while XP is runing, it doesn't mount in OSX however when I shut down XP, the CD mounts in OSX.

I used to have it until I gave OSX CD control.

At this point, I have no plan. I did remove and instll Fusion as well and delete all file execpt for the vmdk file so that a fresh vmx is created but still nothing.

I made the mistake of removing VMWare tools and cannot install them w/o some kind of CDROM.

This pruduct has worked very well for me in XP/Ubunto/Suse/Solaris but you know what they say...

1 aww-shit erases the 5 atta-boys from before.

[admin]

Aha! Details.

In my guest OS (XP), I no longer have a drive letter for the CD/DVD.

OK. So does the CD-ROM drive show up (possibly with errors) in Device Manager? If no, the thing to do is figure out why XP isn't detecting the virtual CD hardware. If yes, the thing to do is check Disk Management to see whether the drive is listed there and why it has no drive letter assigned.

[admin]

Hi, aurfalien. I've been in a situation like what you describe here: where one could not install VMware Tools because Windows believed that it did not have a CD-ROM drive. I don't know whether it's relevant to your situation, but I will describe it here in case it helps.

As of RC1, the instructions for converting a Parallels VM to Fusion involve booting up the old version of Windows, without VMware Tools, in a brand-new VM. Early in my development of these instructions, I found myself unable to install VMware Tools at all in my XP VM because Windows thought it had no CD-ROM drive.

It turned out that Windows XP's device-detection algorithm only discovered the CD-ROM drive after[/b] asking me for a reboot. So now the Parallels migration instructions say: "Boot up the converted VM in Fusion, let it discover devices, reboot when it asks you to, and only then[/b] attempt to install VMware Tools."

So, based on my experience, aurfalien, I'd say you need to...

1. Use Fusion's Settings dialogue to make sure that the virtual CD-ROM drive is present and connected (even though Windows can't see it yet), and

2. Provoke XP to search for new devices (either by rebooting or via Control Panel -> Add Hardware).

[aurfalien]

Hi B,

I removed the device (CD/DVD) in XP and refreshed the device list. XP then found a CD/DVD with an error of;

windows successfully loaded the device driver for this hardware but cannot find the hardare device (code 41)

Any ideas? This sound like a VMWare issue.

Are there any possible tweaks I can do to my vmx file that can fix this?

I'm loosing faith in Fusion.

[admin]

Try removing the device, then telling Windows to search for it again.

[aurfalien]

Hi All,

After many emails with VMWare support whom were very prompt and curtious, they managed to fix the problem.

\** solution **

It's causing like Windows drivers are corrupted for the CD/DVD drive in

Windows XP Guest OS. Please follow the steps to troubleshoot this issue by

manually modifying the windows registry.

Before following these steps, make sure that you back up the registry before

you modify it. Make sure that you know how to restore the registry if a

problem occurs. For more information about how to back up, restore, and

modify the registry, click the following article to view the article in the

Microsoft Knowledge Base:

http://support.microsoft.com/kb/322756

Please follow the below mentioned steps in Guest OS:

Step 1: Start Registry Editor

Click Start, click Run, type regedit, and then click OK. Registry Editor

starts.

Step 2: Delete the UpperFilters registry entry

1. In Registry Editor, expand My Computer, and then expand

HKEY_LOCAL_MACHINE.

2. Expand SYSTEM, and then expand CurrentControlSet.

3. Expand Control, and then expand Class.

4. Under Class, click \{4D36E965-E325-11CE-BFC1-08002BE10318}.

5. In the right pane (topic area), click UpperFilters.

Note An UpperFilters.bak registry entry may also appear. To delete the

UpperFilters registry entry, you must click UpperFilters and not

UpperFilters.bak.

6. On the Edit menu, click Delete.

7. When you receive the following message, click Yes to confirm the deletion

of the UpperFilters registry entry:

Are you sure you want to delete this value?

The UpperFilters registry entry is removed from the

\{4D36E965-E325-11CE-BFC1-08002BE10318} registry subkey.

Note Do not exit Registry Editor. You must have this program for the next

step.

Step 3: Delete the LowerFilters registry entry

1. In Registry Editor, expand My Computer, and then expand

HKEY_LOCAL_MACHINE.

2. Expand SYSTEM, and then expand CurrentControlSet.

3. Expand Control, and then expand Class.

4. Under Class, click \{4D36E965-E325-11CE-BFC1-08002BE10318}.

5. In the right pane (topic area), click LowerFilters.

Note An LowerFilters.bak registry entry may also appear. To delete the

LowerFilters registry entry, you must click LowerFilters and not

LowerFilters.bak.

6. On the Edit menu, click Delete.

7. When you receive the following message, click Yes to confirm the deletion

of the LowerFilters registry entry:

Are you sure you want to delete this value?

The LowerFilters registry entry is removed from the

\{4D36E965-E325-11CE-BFC1-08002BE10318} registry subkey.

8. Exit Registry Editor.

Step 4: Restart the computer

For more details please refer this Microsoft KB article

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B314060