sausisse's Posts

Hello! Windows XP is pretty much unstable these days with VMware. I've tried to replicate this problem and this only happened on XP. I suggest that you get a new motherboard and CPU, since I have ... See more...
Hello! Windows XP is pretty much unstable these days with VMware. I've tried to replicate this problem and this only happened on XP. I suggest that you get a new motherboard and CPU, since I have the same GPU, a slower hard drive (5600 RPM but with 128MB cache) and the same OS. Hope this helps!    
Hello ! Sorry for the late responce, I was busy. I've checked the Monitor Mode and it said ULM. The chipset that is in use is a Intel H510 chipset, used for 10th and 11th gen Intel Processors. I'... See more...
Hello ! Sorry for the late responce, I was busy. I've checked the Monitor Mode and it said ULM. The chipset that is in use is a Intel H510 chipset, used for 10th and 11th gen Intel Processors. I've ckecked to disable Hyper-V but it dosen't appeaur to the Windows feature. Weird. Hope this helps!
I'm not an expert but I think that no software can use a file when Windows Defender is scanning it. It did happened for VMX files butI think that it can happen to VMDK files. Also any kind of restri... See more...
I'm not an expert but I think that no software can use a file when Windows Defender is scanning it. It did happened for VMX files butI think that it can happen to VMDK files. Also any kind of restricition affect the files when applied to the master folder. And for executing to bad drives, it can happen when I/O errors occurs, but I cannot remember if this happened to me, but it can impact the VM, thus causing corruption. I'm not a pro, so I cannot prove anything.
Hello   Yeah I think too. Who would fix sound issues with an 20+ years old OS? But I'ts sad since the problem only appeared with the 17.0.2 version. Just wondering how I can fix this from my side.
Hello. I'm testing a bunch of old Windows imagesfrom the MS-DOS to the XP era and for unknowns reasons, in VMware Workstation 17.0.2, the speed is considerably worse than in VMware Workstation 17.0.... See more...
Hello. I'm testing a bunch of old Windows imagesfrom the MS-DOS to the XP era and for unknowns reasons, in VMware Workstation 17.0.2, the speed is considerably worse than in VMware Workstation 17.0.0 specially in loading and/or playing audio files. Some issues that I've noticed are: 30+ minutes of formatting a 2 Gb drive (MS-DOS) Strugulling to play a 6.22 Mb MP3 file (320 Kb/s of bitrate) with VLC or Windows Media Player (Windows 2000 and NT 4, although this seems like a bitrate issue to me) Hangs (or very slow) while loading setup (Windows XP x64, Windows NT 4.0) Loading issues (Windows 2000) Sound tearing (Windows XP, Vista (unironcally), 2000)   I wonder how that happened and how to fix it.   And in case you wonder, side channels mitigation, even desactivated, is still slow.
Hello,   This is a follow-up to this thread that I've posted earlier : https://communities.vmware.com/t5/VMware-Workstation-Pro/Weird-behaviour-on-some-Windows-NT-4-0-install-CDs/m-p/2945306 To be... See more...
Hello,   This is a follow-up to this thread that I've posted earlier : https://communities.vmware.com/t5/VMware-Workstation-Pro/Weird-behaviour-on-some-Windows-NT-4-0-install-CDs/m-p/2945306 To be short : some Windows NT 4.0 CDs crash the emulated state of the VM. I'm testing (for science) if we can multiboot Windows 11 to Windows NT 3.1. However, Windows NT 3.5 is also concerned to this problem. And not by booting off the CD, also by booting into the hard drive. And litte bonus, I don't know which SP is preinstalled on the CD. I also think that this problem applies to Windows NT 3.51 as this version is build onto Windows NT 3.5, however, I cannot say for sure. And before you ask, yes, I've done the tweaks to do in the BIOS. (Multiprocessor specifiaction to 1.1 as 1.4 crashes the Windows NT 3.x OS)
Hello everyone. When I was testing some of my Windows NT 4.0 disks, while booting of the CDs, after loading all teh drivers required to do the install, some weird patterns appears and the applicatio... See more...
Hello everyone. When I was testing some of my Windows NT 4.0 disks, while booting of the CDs, after loading all teh drivers required to do the install, some weird patterns appears and the application report an error about the virtual CPU shutting down foran unknown reason. What's weirder is after cheching in a other software, these ISOs works, and the same OS doen't crash when SP4 or greater is installed, by default. Also, I think that isn't a setup bug because when loaded on the other software with an different BIOS, that weird pattern doen't appear. Here is all of my tested ISOs that are confirmed having this problem: Windows NT 4.0 Worksation in Korean with SP1 installed onto the disc Windows NT 4.0 Worksation in Swedish Windows NT 4.0 Server in Swedish Windows NT 4.0 Server in Chinese with SP1 installed onto the disc Windows NT 4.0 Worksation in Hungarian   My French discs are not affected because the SPs installed (SP4) apparently is not affected with this problem or the "bug" (in the case of this is a bug in NT 4 that was deteced in the past). A log file is attached in the thread. Thank you in advance.   PS : this was run in VMware Workstation Pro 17.0, but this problem affected the 16.x version, and (if memory serves) the 12.x versions.
Hello Wila, It was effectively the Hyper-V Sheningans that acualy activated. I disabled and it reworks. Thank you !   Sausisse
1 week after the migation of Windows 10 1909 to Windows 10 20H2, when I want to launch a VM, VMware says that I didn't have the XSAVE instruction, and cannot start the machine. Weirder, in Windows 1... See more...
1 week after the migation of Windows 10 1909 to Windows 10 20H2, when I want to launch a VM, VMware says that I didn't have the XSAVE instruction, and cannot start the machine. Weirder, in Windows 10 1909, this message didn't show, and it was running fine. More weirder, after downgrading to VMware 15, it says that I didn't have AMD RVI hardware assisted MMU virtualization, but it didn't say that in VMware 16.1.2 ! It could be related to the processor is too old, but this message pops up since VMware 14, which my PC can run under Windows 7, and I have proof.  So, why?
Hello Wil, I've been busy these times, so sorry for the delay.   The last time I've used Longhorn has 2 years ago, and my knowlege wasn't enough. And I've have 3D acclerelation. So, I disabled an... See more...
Hello Wil, I've been busy these times, so sorry for the delay.   The last time I've used Longhorn has 2 years ago, and my knowlege wasn't enough. And I've have 3D acclerelation. So, I disabled and I updated the compability to 8.x. And I selected a Milestone 6 this whole time. So I switch to Windows Longhorn build 4020, which is a M5 build. And you're right. So, thanks. And to prove that, I have a screenshot of  the VM. Thank you again.   ---------------- Sausisse.
Hello Wil, I understand why you can't help me anymore.   I've tried to install Longhorn on a newer compability, but as I said earlier, DCE will not launch.   The alternative solution that I've h... See more...
Hello Wil, I understand why you can't help me anymore.   I've tried to install Longhorn on a newer compability, but as I said earlier, DCE will not launch.   The alternative solution that I've have is VMware 15. I've tried to get back on 14 back in 2019, but the compability didn't work. Plus, I've have a VMware 16 Player VM, so I can't do that either. We're are at a dead end, unless a employee see the ENTIRE problem, and be capable to reproduce it, and release a patch.   Thank you and I say thanks to whe way out. -------------- Sausisse.
Do NOT use all caps. Everyone thinks that's annoying.   ------ Sausisse
P.S. : I replace the hard drive to at 160 GB HDD to at 1 TB SSD hard drive
Hi Wil, Sorry, I didn't have free time enough these time. So, yes, it boots at VMware 9.x up to 16.x. This is very weird. I disabled 3D accleration and this isn't work. 2 days ago, I booted a VM... See more...
Hi Wil, Sorry, I didn't have free time enough these time. So, yes, it boots at VMware 9.x up to 16.x. This is very weird. I disabled 3D accleration and this isn't work. 2 days ago, I booted a VM of Windows 7 with 15.x compability to wipe a buggy NTFS partition (for personnal reasons) and it booted fine. And yes, my hardware is very old (9 years) and it's listed. It's a Toshiba Satellite C670D-12N. Here the full specs : https://fr.dynabook.com/discontinued-products/satellite-c670-12n/   I don't know why the compability do that.   ----------- Sausisse    
Hi Wil, Thanks for your responce; Since the beggining, I use VMware 16 and it won't boot. But, with older versions of VMware (I used VMware 12, 14 and 15), there are no problem to boot like you sai... See more...
Hi Wil, Thanks for your responce; Since the beggining, I use VMware 16 and it won't boot. But, with older versions of VMware (I used VMware 12, 14 and 15), there are no problem to boot like you said. After a quick look, I remember that early builds of Windows Longhorn, espefically Milestone 3 to Milestone 5 need to be into VMware 6.5-7.x compability mode for the early DCE. (according to BetaWiki) That's why I asked for help because it not boot into this compaility mode on VMware 16. After, NEVER I will put 6GB of RAM into a VM. It's will be more laggier that if I put 1GB. Also, I never touch 3D acclereating for the reason of never touching display adapters. For me, it's just an annoying bug in my version and I don't know why.   Sausisse.
Hi Wil, First, I'm apoligise for be too vague. I post this origial post at 10 PM at Western Europe Time. Second, the compability that I selected is not about vSphere 6.5 because I don't have vSpher... See more...
Hi Wil, First, I'm apoligise for be too vague. I post this origial post at 10 PM at Western Europe Time. Second, the compability that I selected is not about vSphere 6.5 because I don't have vSphere. I select VMware Workstation 6.5 because I want to emulate Windows Longhorn for a personal project. Third, I siad later that I have 4 GB of RAM, and one time, I tired to boot with 6GB, but that reveals faily. Fourth, the version I want to emulate is a 32 bit version. And generally, I put 512 MB fow Windows XP, and 1 GB for higher. Final, I forget to attach the vmware.log file. I will attach here with the VM files.   Again, sorry for be too vague. Sausisse.
It's magic when you upgradeto a newer version, somthing crucial doesn't work. I didn't have this problem in VMware 15, however.
And for the 15.x compabitility.
The evening before this reply, I updated the version to 16.1.2 and the error is still here. Here as sample of a virtual machine on image on 6.5-7.x compability.
Is your hard drive slow? If it is, can replace it? Maybe that can accually help.