Ideal emulators for first-timers

[Windows Thunderstruck]

I am a first timer here, so what would be the recommended emulators for some prototypes (e.g. Windows 3.0, NT 3.x, 1995 builds of NT 4.0, and that Virtual PC 2007 isn't very kind to these builds, eg 5.00.1671, 5.00.2031
I am running Windows 8.1, planning to get a new computer with Windows 10, but I will downgrade to Windows 8.1 if possible.

[geminiman112]

I haven't tried the builds you speak of, but VirtualBox and VMWare work fine for most applications. Try those.

[AlphaBeta]

Use 86Box.

[whistler2250]

I personally prefer PCem v11, it's stable and doesn't constantly give me errors like 86Box does (for running certain troublesome betas).

[WindowsCollector2000]

I started with VirtualBox, it works with nearly any version of Windows, just not 1.0 or 2.0. Also quite simplistic.
VMware contains a BIOS Menu, which allows you to change the date.
PCem/PCem-X/86Box is a bit more complex than the other two, but is the closest thing that emulates an old computer. Perfect for early Windows betas, and early 95 betas. Try not to go past that, unless you want long installs.

[whistler2250]

VMware Fusion seems to work for *SOME* NT 5.0 Builds that get stuck during the guide setup in VirtualBox (aka 1877 and 1888).

[Windows Thunderstruck]

I am planning to use Virtual PC 2007 for builds after NT 4 builds after 1234, they work just fine.
Early NT 5.0 builds do work (e.g 1592 Server) but only as a dualboot with 95 or Memphis/98
Win2K works in VPC '07 as does Whistler, but Longhorn and Vista's performance is disastorious in VPC 2007 espically 5219 and 5231

[Battler]

I personally prefer PCem v11, it's stable and doesn't constantly give me errors like 86Box does (for running certain troublesome betas).

So instead of reporting the bugs and help us getting them fixed, you instead prefer to just go back to an outdated version. Also, what errors doe 86Box gives? With what builds? What configurations? How do I reproduce them?

[Windows Thunderstruck]

I personally prefer PCem v11, it's stable and doesn't constantly give me errors like 86Box does (for running certain troublesome betas).

So instead of reporting the bugs and help us getting them fixed, you instead prefer to just go back to an outdated version. Also, what errors doe 86Box gives? With what builds? What configurations? How do I reproduce them?

For me 86Box complained about a missing d3dx9_43.dll. Is this because I am running 8.1 and not 10?

[RanCorX2]

probably missing the dx9 redist? install that and it should work.

[Windows Thunderstruck]

DX9 Redist?
Where do you find that? I really don't trust Google with stuff like that

[RanCorX2]

DX9 Redist?
Where do you find that? I really don't trust Google with stuff like that

your'll find it here https://www.microsoft.com/en-us/downloa ... Fid%3D8109

[Windows Thunderstruck]

Thanks for that link!

[RanCorX2]

no probs.

[whistler2250]

Most NT 4.0 Builds work just fine in VirtualBox (aka 1130, 1175, 1234, 1293, 1353, 1369), and with the virtual box vbemp driver, the earlier builds are available in high resolution while some of the RC builds will work with guest additions.

[whistler2250]

I personally prefer PCem v11, it's stable and doesn't constantly give me errors like 86Box does (for running certain troublesome betas).

So instead of reporting the bugs and help us getting them fixed, you instead prefer to just go back to an outdated version. Also, what errors doe 86Box gives? With what builds? What configurations? How do I reproduce them?

I used 86Box on My Windows 10 PC for a while, and found it would crash every time I changed the configuration settings with the gui. I ended up having to manually edit the cfg file, which is a HUGE PITA. I went back to PCem v11, and I found it didn't have that same error. This was especially evident when I tried to install Windows NT OS/2 (Oct 1991 Beta). After I changed the CD-ROM drive to scsi, and reset, 86Box crashed on me. I don't like using things that are that unstable. Even Windows Longhorn is more stable than many builds of 86Box!

[TheCollector1988]

You are using an outdated build then. Also, I don't encounter those crashes in the current builds.

[Battler]

- whistler2250: What build of 86Box were you getting the errors with? What I need is, the build number or at least the date when you last used 86Box, and I need your 86box.cfg file.

[whistler2250]

The version was the Core 2 Optimized Version 2.0.0.0

[Machine]
model = ibmpc
cpu_use_dynarec = 0
mem_size = 640

[Video]
gfxcard = cga
video_speed = 0

[Input devices]
mouse_type = msserial

[Removable devices]
fdd_01_fn = C:\Users\ITSupport.ITSupport-PC\Downloads\IBM PC-DOS 3.30 (5.25)\Ibm330_1.img
fdd_02_fn = C:\Users\ITSupport.ITSupport-PC\Downloads\8088MPH_final\8088MPH\dskimage\8088mph.360

[General]
video_fullscreen_first = 0

[CGA]
display_type = 1
composite_type = 1
rgb_type = 0
snow_enabled = 1

[Battler]

- whistler2250: There's a lot of builds of 86Box v2.0 - they get auto-compiled for each commit I make. I'd need to know which you used.

[whistler2250]

- whistler2250: There's a lot of builds of 86Box v2.0 - they get auto-compiled for each commit I make. I'd need to know which you used.

It was one of the early 2.0 builds.

[AlphaBeta]

- whistler2250: There's a lot of builds of 86Box v2.0 - they get auto-compiled for each commit I make. I'd need to know which you used.

It was one of the early 2.0 builds.

Uhh, could you give us at least the last modified date?

[whistler2250]

- whistler2250: There's a lot of builds of 86Box v2.0 - they get auto-compiled for each commit I make. I'd need to know which you used.

It was one of the early 2.0 builds.

Uhh, could you give us at least the last modified date?

Yes, 5/31/2017.

[Overdoze]

Yes, 5/31/2017.

That's horribly out of date. You might wish to try the most recent build.

[James]

Keep this on-topic. This is not a support forum for emulators.

Also, there's a stickied thread at the top of this subforum that has the most popular emulators available right now. This thread is, therefore, pointless.

Locked.