The setup program just create an empty \masm32 folder in C:, then run a VBScript which create a shortcut in my desktop. When I close the setup program, nothing happened in \masm32 :dazzled:
Can V9 work on Windows Server 2003? :red
Thanks
I am pretty sure the problem has nothing to do with the OS...most likely file create permissions on C:...but then how did it _create_ the "MASM32" folder. First thought: rights issue.
Using WinRAR or 7-zip, try extracting the SFX, copying the extracted files into \MASM32 and run the makelibs.bat
shucho,
Just make sure you have write permission as this sounds like the problem. This is a development package so you should have admin access to the OS otherwise a different and limited profile may restrict what you can write to disk.
thank you 2:)
i login as Administrator privilege. and i forgot mention a subtle issue, when i click OK to run the VBScript, i found one .vbs file was created in \masm32, after i close the install program, the .vbs file vanished. so, maybe i have the write permission...
anyway, i will follow shantan's way.
Thank you all.
P.S.
forgive my poor english, chinese is my native tongue :red
shucho,
That is normal with the VBS file, it asks if you want to run it, runs to install the shortcut then it is deleted after the install. The alternative to using the normal install is to use the legacy version as it is identical in what gets written to disk, it just installs in a simpler manner but is larger because of it.
Let us know how you get on as it is useful for other people to know these things.
i just followed the shantan's way, but it did NOT work :(
it seems that the .bat file refused to work. when i follow the "press any key to continue", it just stopped there, nothing happened...
then i opened the makelibs.bat w/ my editor, typed the command in script manually. but bldlibs.bat is also cannot work, it just stopped there, nothing echoed :dazzled:
FYI, my os is Microsoft Windows Server 2003 R2 Enterprise Edition w/ Service Pack 1.
My CPU is Intel Pentium D 2.80GHz.
Maybe the information above help
Hi shucho,
Did you do this...(and exactly this :bg )
1. Extract the m32v9r.zip .zip and you get the install.exe (which is an SFX).
2. Right click on the install.exe and extract to a folder called "install" in the current directory (using WinRAR or 7-zip)
3. Copy ALL the stuff (bin,com examples, etc including all the files) from _inside_ the "install" folder to C:\MASM32 (So now the folder C:\MASM32 has the folders bin, com, etc)
4. Go to C:\MASM32 and run makelibs.bat
P.S.
Its "shantanu" not "shantan" :red :red
Hope this helps.
hi shantanu,
sorry, i misspelled your name :red :red
i followed the steps exactly as you described above, but it does NOT work :(
and i found the qeditor.exe just cannot work, no window displayed, no error messages emitted, just died quitely. :dazzled:
and i just tried the hutch's way, using the legacy V9, it does NOT work either :dazzled:
shucho,
There is something wrong with you machine setup if it will take neither. Be it AV software, trojan damage or whatever else but note that this project has been installed on many server 2003 machines with no problems at all so it is not either installation. You may have configured the OS in an unusual way that prevents disk writes and finally you must have a machine that is capable of receiving an install that is as simple as this one.
shucho,
Too bad it doesn't work. :'( Very unfortunate to hit a roadblock so soon (right at install time)
I myself have installed the same on a 2K3 too. So can definitely say that it works!!!
Hope you can resolve the problem soon to get your ASM coding under way!!! :)
I installed it on a 2k3 server enterprise without problems.
Give the MASM32 folder "Full Control" Security rights to the login you are using.
Just to be sure, we are talking about "C:\MASM32", not a mapped drive? Because I know this trouble sounds too much like a mapped drive installation on W2K3.
Regards, P1 :8)
...and also MASM32 will not install on a network drive. Good luck! :bg
hi,
i manually executed the \masm32\include\inc2l.exe command, but nothing happened, no *.lib file was generated. for example:
\masm32\include\> inc2l.exe gdi32.inc
no gdi32.lib was made :eek
What wrong w/ my computer? :( :( :(
i've just insalled MS Visual Studio. Then i run the MASM32 installation program, the Visual Studio Just-in-Time Debugger reported an error. it looks like:
An unhandled win32 exception occurred in finst.exe [2832].
Maybe the exception caused the installation program cannot work on my computer :(
And, when i manually extracted the file to C:\masm32, then run makelibs.bat, another exception occurred, as reported by Visual Studio JIT Debugger:
An unhandled win32 exception occurred in inc2l.exe [1804].
any solution?
shucho,
There is something radically wrong with your OS installation if these things are happening. The installations have worked on hundreds of thousands of computers including a large number of 2003 machines. A fundamental of an installation of this type is the capacity to be able to write files to disk using published system API functions, if this cannot be done you need to fix your OS.
Your problems still sound like path errors from some form of path remapping. I would take a good look at how your drives are installed on your OS because the installation is designed to be run on a valid disk partition and nothing else.
hi hutch,
I setup only one primary partition on my OS. So there's only a C: driver displayed in windows explorer. And I am sure that I login as Administrator, and Administrator/Administrator usr/group has full control/permission w/ the C:\masm32 directory.
it's really weird. :(
Maybe i have to switch back to my old Windows 2000. :(
Hello Shucho, perhaps try: http://www.safer-networking.org/
hi Mark,
I just tried the software you mentioned above. It found a few cookies.
Then i re-installed the MASM32, it still cannot work. :(
Anyway, thank you for your comments :wink
hi,
can anybody here give me a copy of your installation on "Microsoft Windows Server 2003 R2 Enterprise Edition w/ Service Pack 1." ?
Maybe this way can help
TIA
shucho,
I would be inclined to do a complete re-installation which allows you to set the machine up in a lot more professional manner. Unless you have a very small hard disk, partition the disk drive into 1 primary partition and a number of other secondary partitions then format them as NTFS drives making sure you don't use ANY dynamic disks, drive remapping or any of the other stuff.
Use a normal ADMIN profile to set up any software and if you need it, set up any other user profiles you may require and you should be able to install anything you like. As usual make sure you have no trojans, adware and the like to mess up your machine as they can have unknown consequences that prevent normal operation of many things.
If you have access at Acronis or Norton Ghost disk imaging software, once you get the machine set up and running reliably, make a disk image of your boot drive and store it on one of the tail end partitions so that if something meses your computer up, you can just restore the drive instaed of having to try and re-install it again.
Now, I am using MASM v9 w/ Windows XP. It works well.
Thank you all :U
I also ran into this problem on Windows Server 2003, so I did a little bit of debugging to find out that the cause is software-enforced Data Execution Prevention (DEP). If you use an unzip program to extract the install.exe you would be able to run the makelib without failure by adding inc2l.exe to the DEP exception list in sysdm.cpl > Advanced > Performance Settings > Data Execution Prevention.
Wheet,
Thanks very much for your help here, I develop on win2k sp4 so I have no way of testing these problems. The archive is linked into the installation as an object module which is then written to disk and then run to expand it in place before the libraries are built. Now what I don't undrstand is the effects of DEP with the utility inc2lib.exe as it effectively builds a set of seperate DLLs with empty procedures just to get the import libraries from the DLL build then it deletes each DLL as the lib is produced.
What I don't know here is where data is being run as code.
My drwtsn32 crash logs for inc2l.exe and finst.exe have been posted here:
http://wspe.net/masmcrash/
Hopefully this will be of assistance hutch, I can provide you further assistance if required.
After having a good read of DEP from Microsoft, the problem appears to track down to the "finst.exe" file which is a 7zip SFX archive. It is written to disk, verified as written then run as a seperate process while the installer is disabled.
It is probably the case the "inc2l.exe" faults because soemthing it should have access at is not written when "finst.exe" is running as it does not try to run any data as code. The install.exe does not run data as code either.
I am none the wiser at the moment unfortunately.
Since both crash on a simple PUSH instruction, perhaps the issue involves the stack or stack frame?
I might be wrong on this, but doesn't DEP pop up a warning message rather than terminate with a page fault?
Time to move to NSIS install?!? :bdg :bdg :bdg :green2 :green2
Cheers,
Shantanu
I wondered how long it would take for the suggestion to come up. I have always attempted to be gracious about my comments but with the broken record effort on NSIS, I guess its time to shut it up forever.
If I wanted a commercial installation, I would use Microsoft MSI, or any of the big professional installation packages but I will never use amateurish looking imitations of old style commercial installs. Nor am I even vaguely interested in anything licenced in that manner as the masm32 Project is not beholding to anything and I see the NSIS install as amateurish junk.
Having remembered when I did the installation for masm32 8.2 when I heard this crap over and over again, the problem back then was a defect in Winrar so after tracking it down with the help of some of our members, I opted for the 7zip archiving system which also delivered higher compresion.
I wonder what it takes to connect that I will never use crap like NSIS and if I had to I would use MSI instead.
QuoteI wondered how long it would take for the suggestion to come up. I have always attempted to be gracious about my comments but with the broken record effort on NSIS, I guess its time to shut it up forever.
I myself wondered too (for quite some time) too whether I should say things again which you had already put very clearly before.
Quote...will never use amateurish looking imitations of old style commercial...
...see the NSIS install as amateurish junk
...I wonder what it takes to connect that I will never use crap like NSIS and if I had to I would use MSI instead.
I don't quite understand the "name calling" that you are doing. ::) ::) ::)
You have "connected" perfectly well (time and again) that you are not really interested in NSIS as the installer for the "MASM32 Package".
Thats why I had put those smileys at the end...it was only half-a-suggestion.
Looking at the entire conversation again, maybe I should just PMed you instead of posting the NSIS request openly, maybe the use of incorrect smileys on my part, etc, etc.
Regards,
Shantanu
shantanu,
> I don't quite understand the "name calling" that you are doing.
Simple, I don't like the product and no amount of nagging will change my mind. I have no criticism of anyone else using it but I will never use it as i don't see it as a professional product. If I wanted that type of install I would use a professional product, Microsoft's MSI.
> Looking at the entire conversation again, maybe I should just PMed you instead of posting the NSIS request openly, maybe the use of incorrect smileys on my part, etc, etc.
No, I heard you the first time some years ago and I really am NOT interested but don't let me stop you from using it.
Personally I find MSI's restrictive, and much bulkier.
But to each their own...