Windows compatibility mode
-
The case in point: My Windows 8.1 throws a serious wobbly when it tries to install 32bit Apps form a time when 32bit was cutting edge and will not get past the banner that tells me it can't.
From what I understand, that only happens with 32-bit installers that are actually just a wrapper around 16-bit installers; 64-bit Windows does not support 16-bit programs or installers (except I think there's one in which it substitutes the 16-bit installer for the 32-bit equivalent, but don't quote me on that). A true 32-bit installer will work fine though.
-
Old 32bit apps know nothing about this and want to install in program files.
This is not an issue - assuming you (generic) didn't write your own custom installer. MSI "magically" translates this. So 32bit programs "think" they're accessing ProgramFiles and system32, but thru the magic of redirection are actually accessing PFx86 and syswow64.
My Windows 8.1 throws a serious wobbly when it tries to install 32bit Apps form a time when 32bit was cutting edge and will not get past the banner that tells me it can't .
That is likely because the installer writer is an idiot and is checking something wrong.
edit: And that is the reason there's so many damn compatibility shims in the installer.
-
IIRC, back in the win95 days, installers could well be 16-bit even for 32-bit programs.
-
This pedantry war could go on for hundreds of posts, maybe not in my coding help thread?
-
IIRC, back in the win95 days, installers could well be 16-bit even for 32-bit programs.
Yes they could. Damn it. Because I have a program I need to use for my workflow, which has a 16-bit installer, so I can't install it on a new PC--I have to keep an old one around for that one task.
-
That's what XP mode is for.
-
-
AKA Windows XP running in a 32-bit virtual machine in Windows Virtual PC on a 64-bit Windows host system.
There's a "yo dawg" joke in there somewhere, but I'll let someone else make it.
-
That's what XP mode is for.
Doesn't come with 8/10, IIRC. Plus, then I'd be using XP.
-
Doesn't come with 8/10, IIRC.
It's not supported, but you can still download the XP mode installer, manually extract the .vhd image, and run it in any virtualization suite you like.
Plus, then I'd be using XP.
Make it into a portable app then.
-
Make it into a portable app then.
Why don't I just leave it on the 32-bit Windows 7 PC like I've done for the last few years? Hopefully this spring/summer I'll be able to replace that dependency, as I said above.
-
You made it sound inconvenient to need a separate computer for that software, and I was just pointing out that there are alternatives.
-
There's a "yo dawg" joke in there somewhere, but I'll let someone else make it.
Yo dawg, I heard you like programming so I made x86 simulator in Lua and run it in Lua VM written in my own language which VM is written in JavaScript and ran in JS engine written in C++ and compiled to LLVM bytecode, which I then converted into JS and ran in Firefox inside Ubuntu online presentation opened in Android emulator for Mac OS, which is running in VM under Windows 7 in XP Mode, on VM running inside VM I set on my Debian.
-
Sufficient dickweedery, but lacking pendantry. I give this out of a possible
-
This pedantry war could go on for hundreds of posts, maybe not in my coding help thread?
But now it is jeffed it will fade fast!
Maybe that is the better option ...
-
And? Is it fast?
<there are no trolls here
-
Needs a grayscale version of .
-
-
And? Is it fast?
At the time I wrote that wall of text (about 5 years ago), it ran Doom 2 at 60SPF.
-
Blazing Saddles!
-
-
How many seconds per frame on more modern hardware?
-
Can't get it to run. And I'm not sure which part of that has a problem.
-
it ran Doom 2 at 60SPF
That frame rate sounds painfully like trying to do physics-based animations in Blender on my computer. I routinely get frame rates of ~0.05 FPS while calculating collisions (and all to often failing to detect them), and even playing back the already-calculated animation I often get frame rates between 1 and 3 FPS.
Filed under: I need a better GPU.
-
Now that this is Jeff'd, I can reply!
@PleegWat said:
IIRC, back in the win95 days, installers could well be 16-bit even for 32-bit programs.
Yes they could. Damn it. Because I have a program I need to use for my workflow, which has a 16-bit installer, so I can't install it on a new PC--I have to keep an old one around for that one task.
assuming you (generic) didn't write your own custom installer
Yup. Fucked.
-
Now that this is Jeff'd, I can reply!
@PleegWat said:
IIRC, back in the win95 days, installers could well be 16-bit even for 32-bit programs.
Yes they could. Damn it. Because I have a program I need to use for my workflow, which has a 16-bit installer, so I can't install it on a new PC--I have to keep an old one around for that one task.
assuming you (generic) didn't write your own custom installer
Yup. Fucked.
Or use one Micrsoft didn't bother to compatibilitize, like the Wise! installer.