I am running the RetroNet hub on a virtual machine on my Windows 10 64
bit using Windows 7 32 bit :) So far running smooth. I can also run
The latest Mac OS Sierra on this PC very nicely under VMWare
I understand the Mac OS Sierra on this PC very nicely under VMWare, but why the Windows 7 32 bit? Doesn't Windows 10 64 bit handle Mystic as 32 bit by itself? It should still have a 32 bit stack and I run a number of win32 things that way on the Windows10 boot on this PC. There's also the 64 bit version of Mystic which should work the same with just the executable files replaced like any Mystic version upgrade:
Windows (32-bit native also works in 64-bit): MYS112A31_W32.RAR
Windows (64-bit native): MYS112A31_W64.RAR
That's right from http://www.mysticbbs.com/downloads.html
bcw142 wrote to Necromaster <=-
I understand the Mac OS Sierra on this PC very nicely under VMWare, but why the Windows 7 32 bit? Doesn't Windows 10 64 bit handle Mystic as 32 bit by itself? It should still have a 32 bit stack and I run a number
of win32 things that way on the Windows10 boot on this PC. There's also the 64 bit version of Mystic which should work the same with just the executable files replaced like any Mystic version upgrade:
Windows (32-bit native also works in 64-bit): MYS112A31_W32.RAR
Windows (64-bit native): MYS112A31_W64.RAR
That's right from http://www.mysticbbs.com/downloads.html
Mystic itself does run fine under 64 bit, but if Necro wants to run 16
bit software such as DOS doors, then you really need a 32 bit version of Windows, because the 64 bit Windows OSs don't support running 16 bit
apps. You have to use workarounds like DOSBox, which gets messy.
bcw142 wrote to Vk3jed <=-
At least that makes sense, so instead of dosbox he's using Windows7 to handle DOS/old Windows doors. Dosbox & umsdos aren't as good as 32bit Windows7 for that.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 513 |
Nodes: | 10 (1 / 9) |
Uptime: | 12:27:30 |
Calls: | 8,287 |
Files: | 15,518 |
Messages: | 928,497 |