WhiteTea said:
While at a friend's house I ran some 32 bit programs on his system
that has the 64 bit version of Vista Home Premium.
I am getting the message, "The program has stopped working."
That's interesting.
I did not get that message on Windows Operating Systems from Win 95
-> WinXP.
Is there a way to get it to run?
Is there a Virtual PC available for this version?
Shenan said:
You never said what "it" was. You should contact the support for
"it" and see what they say about running it on a 64-bit system (it
is unlikely (albeit possible) it is a Windows Vista issue when you
also have 64-bit thrown in the mix.)
As for Virtual Machine Applications - VirtualPC, VMware Player,
VirtualBox, etc - all free, all capable of running on that system
and haveing a variety of OSes installed as virtual machines to use
as you see fit - given you have the proer licensing for said OSes.
The program was written using Microsoft's masm compiler and linker.
It is a Vista issue as it ran fine on XP.
Shenan said:
XP 64 bit?
Because - again - you stated this was tested and had problems on a
Vista x64 box.
Please be specific.
It could be a problem in that whatever the program linked to all
this time no longer exists in Vista -and it needs to be recompiled.
It is *not* a "Vista issue" - in that Vista does not need whatever
it is to run - it runs fine without it. It is a problem in how the
application is coded. And again - you have not stated you tried on
a non-64-bit Vista.
It works fine on a non-64 bit Vista systems which includes Windows
95 - XP.
It was recompiled TODAY on a Vista 64-bit system.
It assembled and linked with no errors using Microsoft Assembler
Version 6.14.844.
There is nothing wrong with the way it is coded.
Shenan said:
So now it works fine on non-64bit Vista...?
Before you said, "It is a Vista issue as it ran fine on XP." - but
now you say, "It works fine on a non-64 bit Vista systems". If -
as you say - it works fine on a non-64 bit Vista system, then you
cannot conclude it is a "Vista issue".
Sounds to me like it is a 64-bit issue - as I implied before.
Something about the code is not compatible with 64-bit. Try it on
a 64-bit Windows XP system - does it work?
If not - then something is awry with the code when it comes to
working on a 64-bit operating system. It is not a "Vista issue" if
it works on 32-bit Vista. Actually - again - it is not even an
issue with the operating system - but an incompatibility in the
code itself with said operating system. It's like saying (if it
doesn't work) it is a problem with OS X
10.5... If it wasn't coded to work on it - it's not the OSes
problem.
If you still feel it is a flaw with an OS - I suggest you make a
proper argument (with details) and report it to Microsoft through
the proper feedback channels.
If you made a typo (anywhere) - correct it.
Either way - you need to confirm if it is a "32 vs. 64-bit" issue
or "prior Windows release vs. Vista" issue in the code. It is very
plausible that whatever is in the code doesn't have the same entry
points in Vista or in Vista 64-bit as it once did in older (mostly
obsolete) OSes. I wouldn't expect a Model-T engine part to work
very well in a 2009 Ford either. ;-)
Take some deep breaths.
Things will be OK.
How To Stay Calm and Collected
http://Cool_and_Calm/CandC.html
I hope you have a good day,
I see you have not found the problem with the code yet.
Also have not answered the queries.
Does it work in Windows XP x64?
You said it worked in Windows Vista 32-bit (you said non-64-bit, same idea.)
You also said it worked on Windows 95, 98, 98SE, NT4.0, ME, 2000, XP
(95-XP.) That's fantastic - it must be fairly simple code - so
troubleshooting it should be something fairly straight-forward.
You said you compiled it on a machine and got no errors when you compiled
it - but it only gives you one indication of a problem when ran, "The
program has stopped working." Is there anything in the event logs? Any way
you could build in better tracking /error reporting in the code? Do you
have virtual machines to test upon?
Do you still feel the flawis with Windows Vista (x86 or x64)? If so - have
you actually reported it to Microsoft? This is a peer-to-peer newsgroup and
with the little information you have given about the actual application in
question - it can only be concluded that there is a problem in the code
itself. Just because something compiles with no serious errors does not
mean it will be able to run. Perhaps it needs rights it is not going to
readily have on a UAC enabled Vista system (x86 or x64) or it needs access
to some area it won't have unles you give it rights manually. Maybe it uses
some pathing that remained the same in older OSes - but has changed in the
newer Oses. Perhaps it uses specific environment variables that don't exist
anymore. Perhaps a path it would pick up before cannot be parsed in the
newer OS because it is mor complicated/more spaces.
