Forum Rules - Formats - Spotlights  -  Home - Library - New Additions

Can't run too old OSes on VPC07 on Core i5 hosts?

bigslowfatbigslowfat
edited June 2010 in Software
In Feb. I got a Dell 1564 laptop w/Core i5-430 in.

Since it shipped w/Win7-64,I'v no choice but install a MS-VPC07 SP1 on.WinVPC lacks several functions fatal for legacy OSes to run,while VMware or VBox cannot give a/v functionality on OSes in mid 90s for a lack of drivers.

However,I failed Win95 for a bug about its ndis driver on cpus reporting a speed higher than a certain speed,failed NT31/35 w/a poor perf in text mode inst phase and a registry file missing in startup,and failed NT5 1511 bulid w/a BSOD 0x7e on the very beginning of installation.

VBox do solves the issue,but it uses a unique display adapter that cannot be driven by those old OSes,even including NT4,nor are those accordingly drivers provided by Sun.

Modifing the virtualization option in MSVPC makes no good and I cannot get its reported running speed (to guests) down.

Who have a solution?

Comments

  • nighticenightice
    I'm pretty sure VPC passes through the host's processor ID, which most old OSes don't take kindly to. Have you tried using Qemu?
  • BlueSunBlueSun
    nightice, it does. VMware does it too.
  • UglynGreyUglynGrey
    bigslowfat wrote:
    However,I failed Win95 for a bug about its ndis driver on cpus reporting a speed higher than a certain speed

    You can try the patch here, there is evidence it helps with P4 and later Intels as well as with AMD.

    Full link displayed

    http://download.microsoft.com/download/ ... dk6upd.exe
    bigslowfat wrote:
    ,failed NT31/35 w/a poor perf in text mode inst phase and a registry file missing in startup,

    NT 3.51 is tougher, there's a guide on the net that works well for VPC installs though this was posted in Usenet some time ago by a former employee of mine.

    http://www.eggheadcafe.com/software/asp ... 51-in.aspx
    bigslowfat wrote:
    and failed NT5 1511 bulid w/a BSOD 0x7e on the very beginning of installation.

    too broad an error, try installing on 128 Megs of RAM and then 64 to see if it helps. Try and use a fixed size disk instead of expanding if that doesn't help.

    The old VPC additions from VPC 2004 can be installed for the older operating systems where required and not supplied on VPC 2007.
  • VaultDwellerVaultDweller
    Virtual PC 2004/2007 actually emulates a Pentium III processor, which is why Vista and 7 suck on it :|
  • FedeArgFedeArg
    AntiWin wrote:
    Virtual PC 2004/2007 actually emulates a Pentium III processor, which is why Vista and 7 suck on it :|
    WAT?? NO! :O

    The PIII is emulated on the MAC VERSION only, the windows version (which BSF is going to use) executes the guest os' instructions directly onto the host's processor (Both versions use the Dynamic Recompilation method) :)

    The Main reason of the sucking, however, is the video card it emulates: that sucky S3Trio 64.. which is only (almost) good for DOS games...

    @ BSF: If disabling the HW virtualization didn't help, you can try with Qemu and a GUI.. :)
  • VaultDwellerVaultDweller
    Fede, then explain, why in 2007 SP1, when you check the hardware of the VM, it says

    "INTEL PENTIUM III CLASS PROCESSOR"
  • BlueSunBlueSun
    AntiWin, I don't know about you, but when I check the CPU info in a guest OS under VPC, it says the same thing as my host OS does.

    It's been a while since I last ran a 95 or NT 4 VPC, so I don't remember what they said, but I'm fairly certain it didn't say pentium III...
  • UglynGreyUglynGrey
    Yep, VPC passes genuine CPU ID in all circumstances.
  • stitchstitch
    MacOS Virtual PC passed on a P3 because Windows would have a fucking cow if it passed on information on a PowerPC chip. Most x86<-->x86 virtualizers send and have sent the host CPU information for several, several versions now. Connectix VPC 5.5 was the last to not do this in the Virtual PC market iirc.

    I'll see what I can do about VMWare 7 later.
  • bigslowfatbigslowfat
    edited March 2010
    Some of my attempts:
    I installed a Windows XP guest in VMware and installed a Virtual PC 5.2 inside the virtual machine,also called VM in VM.
    My results:
    1.Windows 95 can now run.
    http://www.flickr.com/photos/48609057@N05/4454506738/
    2.NT3.1 can boot into Windows phase setup but still fails when the setup completes.
    http://www.flickr.com/photos/48609057@N05/4454506516/
    http://www.flickr.com/photos/48609057@N05/4453717741/
    http://www.flickr.com/photos/48609057@N05/4453716921/

    I patched the NT 3.1 files already.
  • VaultDwellerVaultDweller
    Windows NT 3.1 needs a patch to run on anything newer than a Pentium...

    The patch is on OldOs.ORG, last time I checked. :P
  • FedeArgFedeArg
    Well, congratz for getting that NT hell working :P

    I've been into a QEMU 0.12.3 hell during the last 2 days, given up today... I've got too much fail for a TWO DAYS (BSoD hell on the guest W98 OS, fatal exceptions on the whole app) :S

    The only OS which worked flawlessly with interwebz (although without sound because of failing SB16 DOS drivers install and depressing 256-color graphics thanks to a bug) was the infamous WFW3.11 + DOS 6.22 combo.. LOL

    P.S: I know, the official QEMU forum says that W9x sucks under it, dammit :(

    P.S2: What a waste of time, today's the Memorial Day (remembering the start of the military dictatorship which happened here in the 70's) so I've had lots of time on my hands.. ROFL
  • bigslowfatbigslowfat
    An ultimate solution to Windows 9x's zero devision bug:
    tune down the host's CPU speed.
    Obviously, you need Windows Vista or higher which enables you to adjust the highest CPU speed. Windows XP lacks the function.
Sign In or Register to comment.