MSFN Forum: HELP! "Error 1933" when installing VS NET 2003 - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

HELP! "Error 1933" when installing VS NET 2003 Rate Topic: -----

#1 User is offline   XPero 

  • Father of XPize / Vize
  • Group: Developers
  • Posts: 1,912
  • Joined: 08-August 04

Posted 13 September 2004 - 04:02 PM

HI. Ive installed prerequisites successfully, but when i try to install VS NET I got "Error 1933 - Setup was unable to update protected operating system files". :( I have tried a safe Windows XP configuration and i cant install it anyway. They only factor in common in my installations is that they were made with nLite with SP2 slipstreamed. But I suppose that nLite is not the problem.
Anyone using nLite and running perfectly VS NET 2003? What config?
Is VS NET compatible with XP SP2?
Whats the problem? :wacko:
Please help!!!!

Thanks in advance


#2 User is offline   nuhi 

  • ON PAUSE - nLite & vLite human.dll
  • Group: Developers
  • Posts: 4,299
  • Joined: 25-October 03

Posted 13 September 2004 - 05:41 PM

Never happened to me but you can try disabling sfc.

#3 User is offline   XPero 

  • Father of XPize / Vize
  • Group: Developers
  • Posts: 1,912
  • Joined: 08-August 04

Posted 13 September 2004 - 05:47 PM

Ive installed an nlited cd with "safe" settings an with any tweak applied (sfc, uxtheme, etc...) and without any hacked files...i dont know what to do :(

please nuhi give me your nlited config (sounds funny :P ), I will try again :rolleyes:

thanks

#4 User is offline   XPero 

  • Father of XPize / Vize
  • Group: Developers
  • Posts: 1,912
  • Joined: 08-August 04

Posted 15 September 2004 - 09:03 AM

OK the problem was solved :lol: I'll explain what I SUPPOSE was the problem for someone who can have the same problem:

What I used to do was check the option "disable sfc" in nLite and also put in my 386 directory a hacked sfc_os.dll. I think that it is what caused problems.
What I do now and worked installing VS NET 2003 is only check "disable sfc" in nLite and not replacing it with a hacked sfc_os.dll, because nLite does the work fine ;)
No more file protection warnings and VS NET 2003 running fine.

Anyway, thanks for help

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy