Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


ImForrestGump

Member
  • Content Count

    2
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by ImForrestGump

  1. Thank you for the reply. I am using vmware to test. The WatchDriverSigningPolicy would not work in my instance, so I wrote a vb6 exe that basically uses a timer control at 500ms and does an AppActivate "Digital Signature Not Found" and then sendkeys "Y", True. Not as efficient as Pyron's c+ version and is 16Kb vs. Pyron's 4K. This worked for my vmware. Also, I don't know if this is the right forum for video drivers, but you can get more than 640x480 in VMWare during the setup when the logon box finally pops up. After you do the vm iso boot and go through all phases of the setup, you can install the VMware Tools into that instance of vm after initial logon. After that, the video drivers are located in C:\Program Files\VMWare\svga. Copy the 4 or so files to the floppy drive, close vmware so your real PC has access to the floppy drive. Add the VMWare video driver to your driver repository. I also have a Windows Update script that you can call from RunOnceEx that will connect automatically to either a WSUS enterprise server (takes an additional registry hack) or to windowsupdate.com. Then run shutdown.exe to reboot. Now, you can truly start setup and, in an hour or so, come back and windows will be up to date. I know some people don't like wu and actually curse at us who do, but this has helped my company tremendously. I also noticed that I could locate the six or so files from this forum to $OEM$\bin and everything works great. I also changed the default C:\Drivers to %systemroot%\inf\oemdrivers\. This keeps my root of C uncluttered as well as my $OEM$. I already have an inhouse developed utility that I use to set Symantec AV defaults, stores the admin password encrypted (far better than MS way).
  2. I have 4 questions on the Simple Method. 1. Can I delete the C:\Drivers folder in T-13? 2. If my entire Driver collection is compressed, how will Windows respond if I have to reinstall a specific pnp hardware? 3. If I delete C:\Drivers at T-13, what will happen if I introduce a hardware later that was not installed during setup, but was in my Drivers.7z on the CD (all drivers compressed)? 4. Is this compatible with Windows 2000?
×
×
  • Create New...