meik
asked on
32-Bit-Programs don't start
I have two different NT 4.0 Workstation SP3-installations, but some 32-Bit Programs (most of them are Setup-Programs) cannot be executed in NT but in Win 95/98.
When they are doubleclicked (or started in any other way) the cursor changes for about one second and returns to normal state, without any message or action.
Does anybody know the reason of this problem?
When they are doubleclicked (or started in any other way) the cursor changes for about one second and returns to normal state, without any message or action.
Does anybody know the reason of this problem?
most likely, the applications you're attempting to install aren't intended for an NT environment...
ASKER
...they are (e.g. Setup-Program for "CRT for NT")
Check in the registry if .exe is connected to ExeFile and that the shell open command is connected to %1
ASKER
How can I check this? Anyway I think it is as you mean because most programs (about 95 %) start and work correctly.
Even the setup-program for Microsoft Office fails!!??!!
Even the setup-program for Microsoft Office fails!!??!!
happens sometimes to me too.
Rebooting always helps me.
Probably memory leak problems,
or Not enough memory.
Rebooting always helps me.
Probably memory leak problems,
or Not enough memory.
Make sure you don't have a missing DLL. In explorer, right-click the offending program, then click "Quick View". This shows, among other things, the DLLs that the program needs.
ASKER
Sorry Grinch, the Link-Time Imports are Kernel, GDI and User; so it doesn't seem that this's the reason.
It's also no lack of memory and rebooting doesn't help, and it's not a "temporary" behaviour.
Those EXEs seem to be self-extracting-files, and when I load them into WinZip 7.0 I can extract them and everything works. (it was the same with WinZip 6.3)
So any other suggestions???
It's also no lack of memory and rebooting doesn't help, and it's not a "temporary" behaviour.
Those EXEs seem to be self-extracting-files, and when I load them into WinZip 7.0 I can extract them and everything works. (it was the same with WinZip 6.3)
So any other suggestions???
Download filemon at www.sysinternals.com
Filemon will show what files are missing when you try to start the Executable.
Filemon will show what files are missing when you try to start the Executable.
ASKER
Sorry Grinch, the Link-Time Imports are Kernel, GDI and User; so it doesn't seem that this's the reason.
It's also no lack of memory and rebooting doesn't help, and it's not a "temporary" behaviour.
Those EXEs seem to be self-extracting-files, and when I load them into WinZip 7.0 I can extract them and everything works. (it was the same with WinZip 6.3)
So any other suggestions???
It's also no lack of memory and rebooting doesn't help, and it's not a "temporary" behaviour.
Those EXEs seem to be self-extracting-files, and when I load them into WinZip 7.0 I can extract them and everything works. (it was the same with WinZip 6.3)
So any other suggestions???
ASKER
I downloaded a debug-monitor from www.sysinternals.com and it showed me some anti-virus information on starting the program. After removing the anti-virus-software it showed nothing (same when programs worked correctly).
So my problem still exists..... :(
So my problem still exists..... :(
This may be the answer. Look at your config.nt. If there are bad characters inside, you will have problems starting setup.exe.
Download Filemon. It shows you which files are opened and accesses and which open calls failed.
ASKER
Hej! Kuehn's hint was the right one; I had no CRLF between the lines
files=20
device=C:\WINNT\SYSTEM32\D RIVERS\HLL DRVR.SYS
in my config.nt, and after adding that the programs worked.
Kuehn you should answer the question to get the points, thanx to all the other ones who gave me advice!!!
files=20
device=C:\WINNT\SYSTEM32\D
in my config.nt, and after adding that the programs worked.
Kuehn you should answer the question to get the points, thanx to all the other ones who gave me advice!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.