Hello.
I was trying to install Windows 3.0 MME (Tandy OEM) on VirtualBox.
I can't get it to work. No matter what DOS version I'm using, what configuration I'm using, I'm always getting some sort of errors. Here's some of it:
Setup crashes while switching to graphical installation;
Setup graphical installation is glitched a lot (that's a driver problem, I need to use other driver than Paradise VGA 256 colors);
Windows crashes while booting (goes back to DOS);
CPU Error: incorrect opcode while booting into Windows
Hangs at Windows 3.1 logo (what the hell? why there's 3.1?)
DOSBox only: glitched, but something usable; unusable mouse;
I found 2 of Windows 3.0 MME copies, but they are all Tandy OEMs, one of the disks contain Setup and a folder called MMTANDY (all executables want MS Windows), second has some software, Windows and same MMTANDY.
Can someone help me?
Windows 3.0 MME Problems
-
vlad557776
- Posts: 27
- Joined: 19. Feb 2019, 20:52
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Too much to list here (100+ VMs)
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Windows 3.0 MME Problems
There is no guarantee that the Tandy OEM version will work on non-Tandy hardware, particularly when it comes to graphics cards. I assume the original would have been preinstalled or come on a stack of floppies, so this predates the time when the install media was essentially infinite (compared to the actual install set) and you could afford to bundle irrelevant hardware drivers.
-
vlad557776
- Posts: 27
- Joined: 19. Feb 2019, 20:52
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Too much to list here (100+ VMs)
Re: Windows 3.0 MME Problems
Is there any way to bypass this? Maybe there's NOT-Tandy OEM somewhere, I just can't find it...
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Windows 3.0 MME Problems
I'm not sure what you're asking to override. The Tandy OEM install will be intended for Tandy hardware, and probably not even include drivers for non-Tandy hardware.
What is it you're trying to do? If you have a Win16 app you want to run then it should be possible to run it in a normal, supported, XP VM.
What is it you're trying to do? If you have a Win16 app you want to run then it should be possible to run it in a normal, supported, XP VM.
-
vlad557776
- Posts: 27
- Joined: 19. Feb 2019, 20:52
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Too much to list here (100+ VMs)
Re: Windows 3.0 MME Problems
Okay, so there's no way to bypass this. Maybe there's NOT Tandy OEM somewhere...
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 3.0 MME Problems
vlad557776 wrote:I was trying to install Windows 3.0 MME (Tandy OEM)
Yeah, exactly! What are you trying to install and where did you get it from? I hope it's not one of those "museum" sites... If it is, don't bother posting the link, it will be deleted.vlad557776 wrote:Hangs at Windows 3.1 logo (what the hell? why there's 3.1?)
As mpack said, custom-made OEM installations have a really high degree of failure, mainly because you're not "installing" the OS on the OEM hardware, you're installing it on a generic hardware...
I'm having an urge of marking this as NotSupported...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
vlad557776
- Posts: 27
- Joined: 19. Feb 2019, 20:52
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Too much to list here (100+ VMs)
Re: Windows 3.0 MME Problems
I had 2 copies. One copy was downloaded from WinWorld and second from old-dos(a big Russian archive site).