• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Repairing Win2k...

C

Croda

Member
I tried loading VB6 last night on my Win2k system. It hacked up a system file (SYSTEMced???) and the OS refused to boot afterwards. I ran the repair option after booting from the 2k CD. It appeared to copy a whole host of drivers back in. What I'm wondering is whether or not I need to rerun SP1 or not. The system says it is still patched to SP1, but that wouldn't change just due to copying in old files. Does anyone know whether or not this would be necessary?

Also, does anyone know of problems with VB6 and Win2k, or was this just one of those flukey install quirks?

Thanks.
 
Under w2k whenever you apply a SP it should remember that a SP has been applied and would copy the files from the SP rather than the old files from the original CD. However, I am not sure if that's still the case when you do a "repair" option. I guess by the look it should still be ok since it say that it's still on SP1.

Sorry I have no experience with VB6 at all.
 
Anyone else know something about this? I've got a LAN party tonight and would really like to make sure the system is running stable.

Thanks
 
if you're not sure what service pack you're on, and you think there might be hosed up system files, I would install SP2. That will get all the SP1 stuff and more fixes too.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top