>Thx for the reply.
>
>We managed to solve the problem by reinstalling the whole harddisk. We are using win95 and we think the error may be caued by msOffice service pack or by some other DLL files.
>
>
>
>
>>>I'm just guessing, check the config.sys and autoexec.bat files for drivers
>>that are different from existing pcs. It sounds like its a memory problem, or a driver that is causing the memory to hang.
>>
>>Recently my customer bought 4 new PCs. These PCs will hang after these sequences of events.
>>>1. Run my exe
>>>2. Exit from my program
>>>3. Any attempt to run anything will hang the system.
>>>
>>>I tried running it from both the network and the local PCs. Same problem. However all the existing PCs don't give any problem. When it hangs, a black window will appear and I can only cold-boot to restart the system. Please note that other existing sets of PCs are running well and they are running the same program from the network drive.
Robin here, my bet would be on the DLL's from an ( unknown ? ) source. The MS sales force is gung ho on having everyone in the world see the beautiful 'beta' level software of x, y, and of course you can't live without z. In an issue of Infoworld ( glossy tabloid magazine ), in Feburary, there was an article offering a forum to discuss "DLL Hell..." the problem of every app thinking it owns the DLL's for the system. I have had some interesting discussions with others on the UT about DLL's their care and placement, but my guess is a scenario like this: user attends MS sales presentation, comes home with "free" beta-level demo of new x or y or z software, follows at least most of the instructions on installing it, gives CD to friend, forgets about the software and "honestly" answers that nothing has changed on my system....( this is not a technical answer, but I have been bitten so many times by variations on this theme that I am actually beginning to appreciate the MS system info utility despite its slowness of operation and volumninous output )