ralish's Posts

Hello, I wish to report what I believe is almost certainly a bug in VMware Workstation, v.6.0.2. I have a VHD file, capacity of 2GB (growable), that I have split into 2 partitions; technically 3 if you count the extended partition. Thus the layout is as follows: ***1. Primary Partition - 1.75GB - Unformatted (planned as NTFS) ***2. Extended Partition - 0.25GB ***3. Logical Partition - 0.25GB - Formatted as FAT16 When I attempt to map partition 3 of the VHD through the VMware Workstation UI, if the "read-only mode" option is selected, the FAT16 partition mounts fine, as expected. However, if the read-only option is deselected, then the unformatted primary partition is mounted, even if the 3rd partition is clearly selected. Basically, you get a different outcome if read-only is deselected (1st partition instead of selected 3rd). This is an independent VM with no snapshots. I've included the VHD that I am using as a zip'd attachment, so that you can hopefully reproduce what I am seeing. Let me know if I can be of any further help.

I'm having some problems with Microsoft Windows Me that I think can only be described as "bizarre". I'm running VMware Workstation 6.0.2 and have installed a fresh copy of Windows Me in a standard virtual machine (with Windows Me set as guest OS) and no out of the ordinary options or custom vmx file hacks. The problem is that the OS seems to behave very unpredictably when it comes to the successful installation of programs. Now I realise Windows Me is rubbish, and isn't exactly noted for its stability/reliability, but this just seems excessive. I'm running a clean installation of Windows Me (fresh install), with the only third-party software on the VM being the latest VMware Tools (installed immediately after the successful installation of the guest OS). Following installation of VMware Tools, I'm trying to patch up Windows with the latest updates, but installing certain updates successfully is like playing Russian Roulette. For example, I'll boot the Windows Me machine, and attempt to install IE 6.0 SP1, and there's something like a 33% chance that the installation will complete successfully. If it fails (hangs), I'll revert to the latest snapshot (created just before the installation) and try again; sometimes it works next try, sometimes it doesn't. When it does, I'm forced to make a new snapshot, in preparation for the next game of Russian Roulette with the next update. The same process of installation random failures then can be seen in numerous future update installations. Below is a rundown of exactly what I have done in this virtual machine from creation to current: Install Microsoft Windows Me (fresh install) -> Installation appears to go flawlessly, I have reinstalled the OS three times, with no change in procedure, and no new results Install VMware Tools -> Installation appears fine, but requires manual installation of SVGA and Mouse drivers (which I successfully complete) Install Microsoft Internet Explorer 6.0 SP1 (local installation) -> 33% chance of success, 66% of the time the installer will just freeze (hang) Install Microsoft Agent 2.0 (local installation) -> Always works Install Microsoft Data Access Components 2.8 SP1 (local installation) -> Always works Install Microsoft Jet 4.0 SP8 (local installation) -> Usually works, sometimes fails to register a dll Install Microsoft Windows Installer 2.0 (local installation) -> Works Install Microsoft XML Parser 3.0 SP7 (local installation) -> Works Install Microsoft DirectX Media 6.0 (local installation) -> Works Install Microsoft DirectX 9.0c (local installation) -> Works Install Microsoft Windows Media Player 9 (local installation) -> Usually Works Install Microsoft .NET Framework 1.1 (local installation) -> Fails, first message: "Microsoft .NET Framework Setup needs to update the Microsoft Windows Installer components before Setup can continue. Proceed with installation" (choose yes) -> "Setup cannot access Windows Installer components. Setup cannot continue." Install all updates from Windows Update web-site -> See below & Where "local installation", indicates I am installing the program off a local copy of the installer (no internet communication involved) When I eventually get to the stage of installing Windows Updates, it's even stranger, the download of the updates goes perfectly, but then one of the updates will hang while installing perpetually (which specific update appears random). I've found, that continuing to move the mouse while all the patches are being installed seems to increase the chance of successful installation. HOWEVER, once all the patches are installed, on a system reboot, I'm unable to open ANY explorer based window (My Computer/My Documents/Windows Explorer/whatever). The explorer process just hangs! This is on a fresh Me installation, with just VMware Tools, and officially supported MS updates. What on earth is going on?! It should be noted, that over the last few days, I have successfully completed installations of Windows 95 RTM, OSR2, OSR2.1, OSR2.5, Windows 98 and 98 SE, and corresponding updates for all systems, without any issues whatsoever. Further, the Windows 98 SE VM uses ALL the same patches you can see me attempting to install in the list above, and they all install perfectly, so the source installation files are definitely not corrupt. I tried disabling acceleration in the VM (a long shot, I know), but it had no effect. Finally, I remember this problem occurring back on VMware Workstation 5.5, but I didn't bother following it up, so this is not new to Workstation 6. Included as an attachment is my vmx configuration file for the VM. Any and all help appreciated (and desperately needed) :smileyblush:

Hey folks, My machine just 100% froze up a moment ago, no BSOD, just totally froze and unable to get any response from it, hence, I rebooted. Now here's the "great" part, it did so while I was deleting the final snapshot in a virtual machine. I've successfully rebooted, and had a look in the virtual machine in question's folder, and there are 5 disk related files: MOSC - Windows 95 OSR2.1.vmdk MOSC - Windows 95 OSR2.1.vmdk.lck MOSC - Windows 95 OSR2.1-000001.vmdk MOSC - Windows 95 OSR2.1-000001.vmdk.lck Windows 95.vmsd I opened the machine in VMware and took a look at the snapshot manager, and it lists no snapshots, which makes me even more worried than I already am. I have \_NOT_ powered on the virtual machine since the freeze for fear of "finalizing" the damage done, in case something can be salvaged. Have I got any hope of fixing this virtual machine? This is well out of my competency with VMware Workstation... Thanks in advance, Ralish