[Solved/Not-a-bug] Microsoft Memphis build 1351 BSoD

Discussion of development and patch submission.
Post Reply
User avatar
MiraiMiracle
Posts: 43
Joined: Fri 06 Jul, 2018 4:42 pm

[Solved/Not-a-bug] Microsoft Memphis build 1351 BSoD

Post by MiraiMiracle » Tue 05 May, 2020 4:46 pm

Hi there.

I was trying to install Microsoft Memphis build 1351 on my emulated Pentium 66 machine, but it fails with a Blue Screen of Death (exception code 06; invalid opcode) when the setup is trying to install Windows Help. I used PCem version 14 and it works, but on the current version, it does not work anymore. Broken on version 15 onwards. I'm "not" such a old video maker! :?:

HOW TO REPRODUCE:
1. Setup MS-DOS 6.22 with a CD-ROM Extension.
2. Setup Microsoft Memphis build 1351.
3. Finish the setup process.
4. Waiting for Windows Help installing...
5. Blue Screen of Death!
Image attached
Image attached
Screenshot from 2020-05-05 23-37-19.png (5.31 KiB) Viewed 838 times
Microsoft Memphis Build 1351.cfg
Config. file
(1.67 KiB) Downloaded 11 times
Cheers.
Project Fate.Alicia!
Last edited by MiraiMiracle on Wed 06 May, 2020 3:01 pm, edited 3 times in total.
"I should stay rolling as alive and kicking!"

-NANA MIZUKI ACCENT/the Second's catchphrase
Image

SA1988
Posts: 267
Joined: Wed 30 Apr, 2014 9:38 am

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by SA1988 » Tue 05 May, 2020 5:10 pm

Probably bad cpu emulation, also what board? Disable apm and acpi if needed.

User avatar
MiraiMiracle
Posts: 43
Joined: Fri 06 Jul, 2018 4:42 pm

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by MiraiMiracle » Tue 05 May, 2020 8:40 pm

[Socket 4] Intel Premiere/PCI (Batman's Revenge).
"I should stay rolling as alive and kicking!"

-NANA MIZUKI ACCENT/the Second's catchphrase
Image

SA1988
Posts: 267
Joined: Wed 30 Apr, 2014 9:38 am

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by SA1988 » Tue 05 May, 2020 10:22 pm

Try a, e.g.:, the 430VX socket 7 board.

User avatar
MiraiMiracle
Posts: 43
Joined: Fri 06 Jul, 2018 4:42 pm

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by MiraiMiracle » Tue 05 May, 2020 11:30 pm

SA1988 wrote:
Tue 05 May, 2020 10:22 pm
Try a, e.g.:, the 430VX socket 7 board.
Shuttle HOT-557, socket 7 machine, fails booting MS-DOS 6.22 setup with "PRESS A KEY TO RESET" loading crash after a RAM memory detection.

FIC VA-503+, a Super Socket 7 machine, successfully booting MS-DOS 6.22 setup. Booting to normal mode will crash with same exception code, and invalid VxP notice. And the machine goes black and auto-restart. Safe mode works.
Loading crash
Loading crash
Screenshot from 2020-05-06 05-29-55.png (1.27 KiB) Viewed 788 times
Same thing happened
Same thing happened
Screenshot from 2020-05-06 06-00-44.png (5.32 KiB) Viewed 788 times
Invalid VxD notice
Invalid VxD notice
Screenshot from 2020-05-06 06-24-11.png (6.37 KiB) Viewed 788 times
Microsoft Memphis build 1351 safe mode
Microsoft Memphis build 1351 safe mode
Screenshot from 2020-05-06 06-26-56.png (57.84 KiB) Viewed 788 times
Microsoft Memphis build 1351.cfg
Config. file (second edition)
(1.63 KiB) Downloaded 11 times
"I should stay rolling as alive and kicking!"

-NANA MIZUKI ACCENT/the Second's catchphrase
Image

User avatar
leilei
Posts: 777
Joined: Fri 25 Apr, 2014 4:47 pm

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by leilei » Wed 06 May, 2020 1:03 am

Can't reproduce. No BSODs whatsoever when doing it with a Win95B/Win98 bootdisk on a fresh drive (which would be the most sensible way for installing any Win9x in general IMO)

Also with all prototypes, expect "betas" to be buggy. Installing it on top of DOS 6.22 is likely unsupported given it's an early test version (the Memphis Beta Guide recommends only doing it either as a Win95 upgrade or on a fresh disk using a boot disk). Real-mode device drivers especially makes it panic and I certainly wouldn't blame it on PCem when that happens given it's an unfinished Microsoft product produced in the era when mocking Windows for crashing were commonplace...
Flush out your AUTOEXEC.BAT/CONFIG.SYS files.
Attachments
Help installing passes, setup completes
Help installing passes, setup completes
memph1.png (3.19 KiB) Viewed 759 times
First boot works
First boot works
memph2.png (5.99 KiB) Viewed 759 times
The S3 Trio64 driver works, 16-bit color, and an appropriately dated wallpaper is applied.
The S3 Trio64 driver works, 16-bit color, and an appropriately dated wallpaper is applied.
memph3.jpg (142.69 KiB) Viewed 759 times

SA1988
Posts: 267
Joined: Wed 30 Apr, 2014 9:38 am

Re: [Bug] Microsoft Memphis build 1351 BSoD

Post by SA1988 » Wed 06 May, 2020 11:10 am

Starting Windows 9x setup (be it prototypes or finals) from DOS is normal practice... And no, betas don't suck because they are buggy, they show you the evolution of what was in development, if you say that they suck, you'll likely say that finals suck and don't try them as well.

User avatar
MiraiMiracle
Posts: 43
Joined: Fri 06 Jul, 2018 4:42 pm

Re: [Solved/Not-a-bug] Microsoft Memphis build 1351 BSoD

Post by MiraiMiracle » Wed 06 May, 2020 3:04 pm

Tried to fdisk the hard drive with a Windows 98 boot disk, formatted using Windows 95 setup, and it works!!
Microsoft Memphis build 1351 about
Microsoft Memphis build 1351 about
Screenshot from 2020-05-06 21-59-53.png (353.34 KiB) Viewed 641 times
"I should stay rolling as alive and kicking!"

-NANA MIZUKI ACCENT/the Second's catchphrase
Image

SA1988
Posts: 267
Joined: Wed 30 Apr, 2014 9:38 am

Re: [Solved/Not-a-bug] Microsoft Memphis build 1351 BSoD

Post by SA1988 » Wed 06 May, 2020 6:07 pm

Glad to see it works :)

User avatar
leilei
Posts: 777
Joined: Fri 25 Apr, 2014 4:47 pm

Re: [Solved/Not-a-bug] Microsoft Memphis build 1351 BSoD

Post by leilei » Fri 08 May, 2020 4:04 am

My testing was done on both the P60 Batman Revenge config and a HOT-433 PMMX200 config.

I've only bothered with this issue because i've already had this particular build as a vague "Windows 97" zip on a backup around here... i'm not crazy for windows prototypes, i've only had curiously tried a few them while they were new (98 and Whistler mainly), but don't care enough to run those old timebomby buggy no-longer-public builds again.

There could be a rule about not supporting prototype operating systems given instability factors as witnessed here (and maybe also cover the recent 'trend' of new "editions", "ready to run" images, any other form of shameless repack, etc.)...

Post Reply