Jump to content

sho_gun

Member
  • Posts

    37
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About sho_gun

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    none specified

sho_gun's Achievements

0

Reputation

  1. With all due respect, why did you reply to this post if you don't know? My post count may be low, but look at my join date, I've been at this a long time - I really don't need newbie advice.
  2. Can OOBE be removed when you restore your WPA.DBL via $OEM$\$$\system32, or does OOBE need to stay in this situation? TIA
  3. I did what I posted - I never said I couldn't see wireless networks.
  4. <Insert Egg on Face emoticon here> This is not any fault of nLite ... I was using a different set of $OEM$ files for SP3 than I was for SP2. In the process of reviewing new services in SP3 and adjusting previous tweaks I had made to services, I added a registry command to disable the Network Location Awareness (NLA) service to the SP3 files. The SP2 files did not contain that tweak, leaving the NLA service set on manual. With the NLA service set to manual, all works fine as it always has. Sorry to imply that is was a faul of nLite
  5. Regarding an HP NC6220 Notebook. I have used nLite and Ryan's update pack every since I received this notebook a couple years ago and all has always been fine. Problem: When coming out of hibernation mode, the wireless connection shows "Acquiring Network Address" forever. When booting (as opposed to just coming out of hibernation), it connects fine. Additionally, if I install SP3 on the machine - it works fine, this problem is only when I make a slipstreamed install. I have remade the install disc 3 times with same results each time. The last time was with NO addons or update packs at all. Any ideas? Thanks Edit: I just ran a slipstreamed install WITHOUT using nLite and all is fine. This problem happens only after using nLite 1.4.5 and only with SP3.
×
×
  • Create New...