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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About secotton

Profile Information

  • OS
    Windows 10 x64
  • Country
  1. I might suggest that if you're using WinPE to deploy Windows 7, you use DISM to deploy the image and inject drivers into the image while in Windows PE. That's how I'm doing it with a custom AutoIT script - it deploys a WIM image, and detects / installs the correct drivers based on model. You just need to select 3 things in the script - WIM image, Target, and base location of the drivers. It's a very similar method that Microsoft's SCCM would deploy Win 7.
  2. I ended up writing an AutoIt script that allows a tech to select a WIM file from a standard file select dialogue box. # File Open Dialog Box FileOpenDialog ( "Select WIM file", "", "WIM(*.WIM)") I forget which one it was, but I think getting a file select dialogue box to work in VB/HTA was next to impossible....or at least it was messy. I moved to AutoIt - a bit of a learning curve, but it was worth it.
  3. We did the exact same thing as you described - the acpi_pc HAL would boot everything...while until we got the latest Lenovo T400's in. The processor in that model doesn't support the ACPI_PC HAL - apparently Intel decided to remove some instruction sets that were outdated in favor of newer ones (don't quote me on that). I've now decided to 'fork' the image since alot of the older computers are too old now and not being used as much. The dual core's really do pack a good punch compared to the P4's.
  4. That should work as well. I just tested this morning using the method I've used, and it worked wonderfully. dkreifus - I'm just wondering how you go about detecting the processor?
  5. I'm in the same boat as you - we just got our first T400 in, and the standard image doesn't boot - it just black screens. Nothing happens at all. I did some quick reading and a few people were saying the new procs in the T400 only like to boot with the ACPI MultiProcessor HAL. One thing that could be done is to force a specific HAL to be used at boot time. This can be done using the KERNEL and HAL switch in the boot.ini. Check out my post at: http://www.msfn.org/board/Increase-Hardwar...359#entry774359
  6. One thing that comes to my mind is this - are there any programs installed that changed anything to the network components? I have found that VMWare slows the network process down a small amount, and I once put Cisco VPN onto an image then did sysprep, and this slowed the network section of the mini sysprep down considerably.
  7. I've decided to change the HAL type once in the OS using a VBScript. It's not quite as nice, but it works for me very well. It changes the HAL by modifying the boot.ini to include /kernel=ntkrnlmp.exe /hal=halmacpi.dll. Basically, it gets the processor name, and compares it against a list of processors that I put in at the top of the VBScript in an array. I only really enable the MP HAL if the computer is a dual core computer, otherwise, ACPI works for pretty much everything else just fine. I've done some speed tests, and haven't found any issue in running with the ACPI HAL versus the ACPI Uni HAL.
  • Create New...