Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VS6 Pro, NT4, logout error
Message
General information
Forum:
Visual C++
Category:
Troubleshooting
Miscellaneous
Thread ID:
00143541
Message ID:
00145609
Views:
37
>If you had visited Microsoft recently they just announced a service pack for Visual Studio 6 yes that soon :-( It may solve your problem but then again it may not. Good Luck anyway
>
>Jean-Luc

Merci Jean-Luc!

I have seen that, but unfortunatly my symptom doesn't seem to be covered by that update.

I have done additional testing, and here are the results, so if anyone knows anything, please contact me!

The system:
Asus P2L97 motherboard
Intel Pentium II 266Mhz
2x 64Mb DIMM (total 128Mb)
NT4 Workstation
ATI Xpert@Work AGP 8Mb
HD Seagate IDE 6.4Gb UltraDMA
Sound Blaster AWE64 Value
Anything else of importance? :-)

I can reproduce the problem at will. I just need to log in and log out (as any user, including Administrator). No need to run anything. The first logout will be fine (and sometimes the second too), but then every logout gives me the following error:

Explorer.exe - Application Error

The instruction at "0x4a00868" referenced memory at "0x4a00868". The memory could not be "read".


I did a parallel install of NT (in another directory). Right after installing NT, I installed VS6 with the default settings. I did not even install any video drivers or service pack (VS6 installed SP3 and IE4 of course), network drivers, sound drivers, and the problem is still there, so I think we can rule out other programs as beeing the cause. Note that I haven't installed any hotfix. I did not install networking (trying to keep NT as simple as can be). I took a look at the hotfixes available but couldn't find anything near my problem.

I have also tried swapping my DIMMs; same error, same address. Tried with only one DIMM at a time (it's hard to get down to 64Mb <g>); same error, same address with each DIMM. I am going to try with completly different DIMMs tomorrow, but at this point I expect the same result; I just want to have an answer should Microsoft tell me it's my memory! I would like to try with a different machine, but I don't have a suitable one I can use.

Anyone with NT ever got a similar problem?

Sylvain
blackphoenix@cablevision.qc.ca
Sylvain Demers
Previous
Reply
Map
View

Click here to load this message in the networking platform