Jump to content

toastycheese678

Member
  • Posts

    64
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by toastycheese678

  1. Oh and you can remove

    KB933824 - An Apple iPod may be corrupted when you eject it by using the "Safely Remove Hardware" feature or by using Windows Explorer in Windows Vista

    from your update list because it has been replaced by

    KB936824 - The Safely Remove Hardware feature and the Windows Explorer "Eject" command do not work correctly with an Apple iPod that is connected to a Windows Vista-based computer

  2. The most annoying bugs fixed by Non Public Updates

    Do you guys include those by integrating all of them into your install.wim? Or do you just install them when the issue occurs?

    Also have there been any updates to this list since March?

    Thanks

  3. Alright third test results are in. Same thing has happened. I checked device manager and kept it open while removing devices and my video nor my audio unknown devices were removed. devcon32.exe was running at 100% the entire time. After ending the process I let it run and nothing happened.

    Then I manually removed those two devices and it detected the only root\serial device. I couldnt remove that device because I dont even know what it is talking about. Same thing happened. I ended the devcon32 process and the program went through finishing up the rest of its stuff. It finished by saying it didnt install any drivers and that it would terminate in fifteen seconds. However, it never did. The process services.exe was running at close to 100% and I couldnt manual end a windows process.

    Here are the ini and log files again. Now ill just try each specific version but dont get your hopes up.

    Is it possible that a new Windows update is causing these issues? Just a thought

    hardware.log.txt

    hardware.ini

  4. Second try and same thing happened. However, It still recognized the serial device as a problem even though I set the ini file to only worry about problem IDs 28.

    Next test I will try to run 6.6 with the device manager open, hopefully seeing if any devices are removed.

    Heres the modifed ini file I used and the second log file

    If you have any specific requests for test runs let me know asap

    hardware.ini

    hardware.log.txt

  5. I tried the earliest 6.6 version and I still froze up. I couldnt pull the log file because my entire computer locked up. Additionally, my cpu percentage usage is 0% but the computer is still locked up. I can move the mouse but thats about it.

    One thing that might be a problem is that the program is finding my audio and my video drivers which are not installed by default on the testbed, but it is also finding a :

    NR - 3

    Device ID - ROOT\LEGACY_SERIAL

    Device Name - Serial

    Problem ID - 24

    Could this be the problem? I will try to run the program with advanced settings ignoring Problem ID 24 and just do 28 for the other two drivers

    Heres the log for this first test:

    hardware.log.txt

  6. Madboy

    So i just saw that last reply today and thought hmmm.... I never got an email from Madboy. I just thought you were busy or testing yourself. Sure enough I go and look in my spam folder right now and there it is. :whistle: Good news is I have a testing environment setup that I can use today so your results should be available within eight hours, depending on how much other work I must accomplish.

  7. Hey no problem. These were two test machines that nearly a second ago finished installing Windows XP. Popped back in the unattend disk and we were back in half an hour.

    Just like to say that from what I saw in the GUI I was extremely impressed. I am installing Windows XP over the network using Windows PE and needed some way to take care of drivers recursively scanning a folder on the network. This correctly identified the two devices missing and not any more than that. Keep up the good work!

  8. [GuiUnattended]

    DetachedProgram=".\system32\cmd.exe"

    Arguments="/Q /C FOR /F %I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %J IN (%I..\..\$OEM$) DO (IF EXIST %J (start /min /D%J Drivers.cmd)))"

    If I want to install XP through the network instead of through an installation disk, what do I need to change in the above code to point the $OEM$ folder to \\server\xp\i386\$oem$

    Thank you

  9. So I tried this program for the first time today and have a couple of questions. I run this program and it finds the unknown devices and attempts to remove them. As soon as the first one starts to uninstall my whole machine slows to a crawl and I am unable to do anything. I left it like this for approximately five minutes and after no progress I restarted the computer. Windows XP progress bar finished and was just about to boot to the desktop when I get a black screen and the machine is frozen. I tried this on two different machines and both resulted in the same thing. My hardware.ini

    [iNFO]

    Start=Automatic

    Drivers_drive=Relative

    Drivers_dir=\Drivers

    Device_manager=Off

    Method=RegistryDevicePath

    Drivers_Packed=No

    Copy_drivers=No

    Copy_where=C:\Drivers

    Delete_drivers=No

    Create_backup=No

    Update_All_Drivers_Version=No

    Time_to_start=0

    [LOG]

    Logging_to_file=Yes

    log_file_name=hardware.log

    log_path=&ProgramDir

    Logging_option=Simple

    The S drive is a mapped network resource but that should not matter at all, right?

  10. I am currently having problems with WinPE 2.0 and XP install. I am trying to use one WinPE disk to install both XP and Vista. I have the disk set so that the Vista install initiates. Then I create the partitions I want through Vista Setup. If I hit next then Vista installs on the C: Partition. If I exit the Vista Installation after the partitions are created then XP tries to install on the C: Partition.

    After creating the partitions and exiting the Vista Setup I am sitting with a 40 GB C Partition and a 120 GB D Partition. I then run the following commands:

    Diskpart

    Select Disk 0

    Select Partition 1

    Assign Letter C

    Active

    Exit

    format c: /fs:ntfs /q /y /v:Boot

    \\XP\I386\winnt32 /s:\\XP\I386 /unattend:\\XP\I386\winnt.sif /dudisable /syspart:c

    This copies over the installation files for Windows XP to the local machine. The computer is then restarted

    Immediately following the POST i receive the following message:

    A disk read error occurred

    Press Ctrl+Alt+Del to restart

    I tried updating the bios of the motherboard and using bootsect.exe /nt52 c: /force, and changing the disk type to Auto, CHS, Large, LHS

    Ive also integrated the following registry entries into my WinPE disk

    reg load HKLM\PE-SYS c:\Winpe_x86\Mount\Windows\system32\config\system

    Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /f

    Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /f

    RegAdd "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /f

    Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /f

    reg unload HKLM\PE-SYS

    All result in the same error

    Any ideas?

  11. I think this may be becuase of your starnet.cmd file. I am currently installing vista over the network so I am in the same boat as you. I keep the entire source directory available and the setup.exe file. Then, after wpeinit is loaded completly, I type "net use P: \\server\vista" to map the network drive and 'P:\setup.exe /unattend:"P:\ConfigurationSet\AutoUnattend.xml"' to start the install. Now of course you will have to change the references for your own personal settings.

    There is another way to implement these commands into your winpe disk. After opening up the WinPE image, edit the startnet.cmd in the system32 directory. Add those lines to it after the winpeinit command. Let me know if this helps.

  12. I have had that problem too. The answer: SkipMachineOOBE. For about five minutes setup is testing the performance of your computer. If the SkipMachineOOBE is set to 1 than you will not see it test the various components and instead receive a blank screen to essentially "skip" the testing phase. It still tests your computer you just do not see anything.

    The same may be true for SkipUserOOBE but I have not tested this theory yet.

  13. i was trying to do the same thing as you were. I couldnt get it to work. However, I did manage to find a work around. First, create a temporary account

    <LocalAccounts>

    <LocalAccount wcm:action="add">

    <Description>Temporary</Description>

    <DisplayName>Temp</DisplayName>

    <Group>Administrators</Group>

    <Name>Temp</Name>

    <Password>

    <Value>REMOVED</Value>

    <PlainText>false</PlainText>

    </Password>

    </LocalAccount>

    </LocalAccounts>

    Then set your autologon as follows:

    <AutoLogon>

    <Enabled>true</Enabled>

    <Username>Administrator</Username>

    <Password>

    <Value>REMOVED</Value>

    <PlainText>false</PlainText>

    </Password>

    </AutoLogon>

    Then i set up a run once batch script to delete the temporary account.

×
×
  • Create New...