I installed Windows Chicago build 122 in Microsoft Virtual PC 2007, but when i login, the display is corrupted.
Does it have something to do with the S3 Trio64 adapter with Virtual PC 2007? I installed build 490 and there was no display corruption.
Display corruption in 122
-
Windows Thunderstruck
- Posts: 583
- Joined: Tue Aug 08, 2017 2:11 pm
Re: Display corruption in 122
Use 86box or PCem for that build.
Also about 86box's missing d3dx9_43.dll, search directx june 2010 and click on the download.cnet.com link.
Configuring 86box is rather similar to PCem.
Also about 86box's missing d3dx9_43.dll, search directx june 2010 and click on the download.cnet.com link.
Configuring 86box is rather similar to PCem.
- MCpillager12
- Posts: 362
- Joined: Wed Apr 17, 2019 12:44 pm
Re: Display corruption in 122
Just made a new machine in PCem.Windows Thunderstruck wrote:Use 86box or PCem for that build.
Also about 86box's missing d3dx9_43.dll, search directx june 2010 and click on the download.cnet.com link.
Configuring 86box is rather similar to PCem.
Right now I am configuring the HDDs.
*EDIT*: Its extremely slow, even though I configured an Pentium Overdrive MMX 180 and 64MB Ram.
Last edited by MCpillager12 on Sun Apr 21, 2019 6:55 am, edited 3 times in total.
-
Windows Thunderstruck
- Posts: 583
- Joined: Tue Aug 08, 2017 2:11 pm
Re: Display corruption in 122
Don't forget to choose the Trident monitor in the settings!
If you want a higher resolution that is and not have an invisible mouse cursor.
If you want a higher resolution that is and not have an invisible mouse cursor.
- TheCollector1988
- Donator
- Posts: 3604
- Joined: Wed Feb 23, 2011 12:11 am
- Location: Italy
- Contact:
Re: Display corruption in 122
Well, s3 801/805 (built-in) drivers work fine there, as do 189 s3.drv/vxd drivers on this build (you can even get up to 1024x768x32bpp with such).
-
.NETLover3790
- Posts: 42
- Joined: Sun Jun 09, 2019 1:59 pm
Re: Display corruption in 122
I have a similar issue in the RTM of Windows 95. It simply detects the "S3 Trio" as "S3" and uses the wrong display driver, causing display corruption. However, once I set it to a generic VGA driver in Safe Mode, it autodetects it before fully booting into the OS.