Forum Home
Press F1
Thread ID: 4293	2000-05-17 13:39:00	Invalid VxD dynamic link call from VWIN32(04)+000015C0 to device 0002, service 1	Guest (0)	Press F1

Post ID	Timestamp	Content	User
4765	2000-05-17 13:39:00	Local computer shop (now gone!), added a 2nd HD of 6 . 4G in 3 partitions D,E & F to my 1 . 2G HD, increased RAM from 16 to 48 and installed NSW2000v3 . 0 . Problem was created by installing NSW over an existing version of Norton Anti-Virus, NAV was on C drive and NSW installed to D drive, parts of the programme were just not working . Checked Symantec Knowledge Base and best option appeared a complete manual uninstall . Followed it to the letter and appeared to successfully re-install NSW on D drive . Have been running with no problems for approx 5 days when the message above 'Invalid VxD etc' appeared on a blue screen with the additional text, 'Your windows configuration is invalid . Run Windows setup program again to correct this problem . I closed windows and rebooted to check Norton Crashguard which reported Windows 95 Version 4 . 00 . 950SYSDOC32 caused a general protection fault in module USER . EXE at 000f:00001894 . Registers:EAX=00001d97 CS=1787 EIP=00001894 EFLGS=00000202EBX=212f7000 SS=279f ESP=00007ba4 EBP=00007bf8ECX=0000b160 DS=1d97 ESI=00002f8f FS=0000EDX=0000279f ES=0157 EDI=00000157 GS=0000Bytes at CS:EIP:2a 00 08 e9 1c f6 8b 5e f4 f6 47 2a 02 0f 84 11 Stack dump:1dbf0599 00000200 00010000 2f8f0157 01870028 00000055 bff7a817 815c98f0 000000f7 0070ec64 815eacf8 00000000 7eb9c297 00707000 0000000f 7eba7328 After trying to close down I then got an MSGSRV32 Illegal Op . , GPF in USER . EXE @ 000f:00000515, tried to restart the computer and got a lock up . At a loss what to do I hit reset and ran WinDoctor which analysed 2 problems of missing or invalid keys: CLSID79eac9d0-baf9-11ce-8c82-00aa4ba90b}\InprocServer32 . and CLSID79eac9d1 . . . etc . The notation above these detailed faults read 'Directory \WINDOW\SYSTEM moved from drive C to C . A removeable drive has been inserted or removed, or a directory was moved to a new drive causing drive C to appear as drive C . These problems should not be fixed automatically . ' At that point I decided I was lost in space and should try this F1 I had read so much about . Funny thing is everything still appears to be running OK . Heres hoping George Woods	Guest (0)
1