I'm trying to install TWGS v3.13b on an NT4.0 server. The install process keeps getting an access violation on WINNT/SYSTEM32/GDI32.DLL. The install just quits.

This .DLL seems to be constantly in use. I've tried stopping all possible services and processes but still the same result.

Has anyone experienced this and/or know of a workaround?

I wish I had more info about the problem you are haveing, so I can replicate it on my server, I have windows 2003 server and the only problem I had from the TWGS was it didn't want to go on line then when i figured out I had to kill the telnet of the server I still could not get a connect to the TWGS then I had to go to the IP filters and set them to allow, when that didn't work I went and checked, and lo and behold microsoft had a second set of filters that were almost identical to the first set that were (if checked ) set to block, thats right they were set to do the opposite of the other filters when checked, I don't know if this helps you but that was the problem that I faced and had with my version, but afer a long session of adjustments it worked. If you can give more specific details of exactly what it is doing and I can research it and see if I can help. Also you might have a corupted download. Sometimes the download can get corupted while downloading, and this can cause all sort of errors, that happened with my SWATH, when I deleted it and redownloaded it, it worked. What I am saying is that sometimes anything can happen while downloading that can corupt a file being downloaded. Try uninstalling and deleting all instances of the TWGS from your server and get another copy downloaded from EISs beta site, making sure you have anything that can interfere with the download turned off when you download the TWGS again, my coruption came from my antivirus scanning the file while downloading it and the pause evidently caused it to not get all of what it needed to work, so I turned off Nortons for that download to get it complete, then I scanned the file after the download to be safe, then reinstalled it and it worked. try this and see if it helps and let me know, if you still get this error, then email me at this email and include the screenshot ot what it is doing. with a full description. And I will see if I can help you with it.
My E-mail vulcan219@comcast.net
Sorry this post is so long!


Vulcan

I am getting the following application event error message when trying to install TWGS on my NT4.0 sp6a server:

Exception code: C0000005 ACCESS_VIOLATION
Module: C:\WINNT\system32\GDI32.dll
Function: 0x77ed59b6
=====================================================

Registers:
EAX:000A3A90 EBX:0001F388 ECX:000041F3 EDX:00070548 ESI:01BEEFFE EDI:000B264C
CS:EIP:001B:77ED59B6 SS:ESP:0023:0006C7A4 EBP:0006C7C4
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010206

Call stack:
Address Frame
77ED59B6 0006C7C4 0
-- 0x01010046 0x01BE001A 0x00000004 0x01BE0442

I am getting the following application event error when trying to install TWGS on my NT4.0 sp6a server:

Exception code: C0000005 ACCESS_VIOLATION
Module: C:\WINNT\system32\GDI32.dll
Function: 0x77ed59b6
=====================================================

Registers:
EAX:000A3A90 EBX:0001F388 ECX:000041F3 EDX:00070548 ESI:01BEEFFE EDI:000B264C
CS:EIP:001B:77ED59B6 SS:ESP:0023:0006C7A4 EBP:0006C7C4
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010206

Call stack:
Address Frame
77ED59B6 0006C7C4 0
-- 0x01010046 0x01BE001A 0x00000004 0x01BE0442

quote:Originally posted by spydude

I am getting the following application event error when trying to install TWGS on my NT4.0 sp6a server:

GDI32.DLL is the graphical device interface Windows NT uses to create two-dimensional images. A lot of GDI32.DLL problems are related to poor NT drivers for graphics cards. It could also have to do how repaints are handled by the application and whether there are sleep routines between window repaints.

can't you just talk in English. geeze, I have a headace now

You could also check with your manufacturer of the graphics card and see if they have an update or patch for your video card, unless it is built in the mother board, then you have to check with the mother boards manufacturer in some cases. You might have a bad or outdated driver.

Vulcan