puzzling occurences in MASM32

[shankle]

Running windows7 pro 64-bit on an HP puter.
This is the 2nd time that I had to reinstall MASM32 from a backup.
I know you are going to tell me MASM32 should not be run on a 64-bit
puter. BUT most of the time it works.
Have MASM32 installed in a separate folder.
Here is what's happening.
When I try to compile a program the compile doesn't take, changes
made to the program are not updated, fonts sizes change drastically.
Can not pin down why most of the time there are no problems
doing this and then chaos. My solution is to delete the MASM32
folder and reinstall it. YUK!

[qWord]

sounds more like that your AV doesn't like the assemble/link process?

[CommonTater]

Running windows7 pro 64-bit on an HP puter.
This is the 2nd time that I had to reinstall MASM32 from a backup.

The next question is: Where are you installing MASM?

I don't know the specifics of MASM or your IDE (if you're using one) but Win7 can get a bit snarky about programs installed outside the c:\program files and c:\program files (x86) folders.  The tendency seems to be to virtualize settings and user data folders, putting them in places you don't expect. 

Also, when you get MASM installed again, go to each of it's executables, right click then Properties -> Compatibility and check "Run as Administrator" which gives you heightened privledges when running your builds.

[jj2007]

Masm works like a charm on Win7-64. I even gave it an own drive with SUBST.

[qWord]

but Win7 can get a bit snarky about programs installed outside the c:\program files and c:\program files (x86) folders.  The tendency seems to be to virtualize settings and user data folders, putting them in places you don't expect.

I'm using Win 7 (x64) for several years and also with programs that resist outside the Program folder - I never had such problems (or I can't remember of).
But I've had problems with my AVs which don't like compilers and assemblers because they create/modify executables.

[CommonTater]

But I've had problems with my AVs which don't like compilers and assemblers because they create/modify executables.

Which is why I don't run anti-virus software.  Really... none.

Joe Average has very little to worry about in terms of hackers and invaders.  For the most part their files are just a bunch of pictures and maybe a few movies... nothing even worth a hacker's efforts. Most of the real bad boys put their efforts into government and corporate systems, where the big secrets are kept. 

My system is firewalled through a router... inside the lan it's all wide open... and never one problem from viruses or trojans.  A little common sense --Noooo, don't install that tollbar!  ;) -- is often your best anti-virus tool.

[qWord]

Which is why I don't run anti-virus software.  Really... none.

you are an optimist 

[shankle]

Thanks guys for responding.
I used an incorrect word - "Folder" - should have used partition.
Masm32 resides in its own partition, GoAsm in another partition,
C in another partition.
I have no way of knowing if ESET SS is the culprit. It has served me well
in the past. I would NEVER go on the internet without a virus program.
ESET SS never gave me any MASM32 problems on my 32-bit puter.
Sorry I don't agree with you CommomTater.
So JJ2007 I assume you are using a virus program. If so which one please.
And Qword which virus program are you using?
Have this thing about Mcafee and Norton - I avoid them like the plague.
Please feel free to correct if I have stated anything wrong or ridiculous.

[CommonTater]

Sorry I don't agree with you CommomTater.

LOL ... No worries ... I get that a lot.  :icon_confused:

[shankle]

Not to worry CommonTater. We agree to disagree.
Using Sandboxie and ESET SS interactive mode gives
me the shivers. Tons of stuff are stopped by these two programs alone.

[qWord]

Maybe the problem is that some of your projects use absolute paths to C:\masm32 while building?

[CommonTater]

Which is why I don't run anti-virus software.  Really... none.

you are an optimist 

And lucky too ...

From 1999 to 2006 I ran a single installation of Win2000 on my programming machine.  It just worked.
From 2006 to 2011 I ran two installations of XP. The first one I mangled in a week.  The scond lasted nicely. 
From 2011 to Present I've run a single installation of Win7x64 and since I shut down all the background crap it just works.

Mostly I just get things stable and leave them alone...  No Background defrags, no Automatic Updates, no Background Intelligent Transfers, no AV software and even the Windows firewall is shut down. 

The current uptime on family server is in Months ... would have been years except for a HD failure.
The HTPC (XP / ATOM) has been on for nearly 2 years.
My smarter half's home office system has been running for several months.
My programming machine is shut down each night and restarted each morning.

It's like my father told me when I signed up for electronics courses... "Remember son, if it ain't broke, don't fix it!" ... he was joking, of course... but he was also right.

The guys with all the AV and software firewalls, toolbars and fancy gadgets on their desktops pay me some pretty good money to get their systems straightened out... So I don't mind. 

[CommonTater]

Maybe the problem is that some of your projects use absolute paths to C:\masm32 while building?

They might also be using environment variables that make similar references... %path% and %homepath% are likely candidates.

[jj2007]

Maybe the problem is that some of your projects use absolute paths to C:\masm32 while building?

That's a pretty fretty frequent problem. \Masm32 is fine, C:\masm32 is crap.

They might also be using environment variables that make similar references... %path% and %homepath% are likely candidates.

One of the cute "improvements" made by our friends at Redmond is this:

The case of %ProgramFiles% or %commonprogramfiles% must be exactly as shown because the string comparison is case-sensitive. For example, if the string begins with %CommonProgramFiles% instead of %commonprogramfiles%, it is not replaced.

If Bill Gates could be held responsible for the extra work caused by Windows' flaws and dirty tricks, he wouldn't be one of the richest men in the World but rather a poor inmate :icon_mrgreen:

[CommonTater]

Not to worry CommonTater. We agree to disagree.
Using Sandboxie and ESET SS interactive mode gives
me the shivers. Tons of stuff are stopped by these two programs alone.

http://www.ngohq.com/news/19466-eset-update-brings-mass-false-positive-alerts.html