cdob

WLAN is connected at USB bus internally. Hence the USB list. LAN and Audio are connected to PCI bus. ICH7 reminds to Intel 945 chipset. Get relating chipset and graphics drivers. Open device manager, select hardware. View details, scroll to HardwareID.Search this HardwareID on the net.

How does device manager list this devices? Which MDG Netbook do you use at all? Do you have a manufacturer link? How are WLAN and audio are connected internally? Do they use USB bus? Can you name the relating HardwareID's? I doubt issue is caused by installing from USB.

At VMware and different real hardware: iastor.sys 9.x BSOD ocassionally at IDE mode. iastor.sys 8.x and 10.x does work fine. Overall: Avoid iastor.sys 9.x at dual usage XP installations. Use iastor.sys 8.x or 10.x

Try Intel (RST) 10.0.0.1046 WHQL too.

Windows setup search files at first partition. Can you delete file ei.cfg at first partition?

I don't understand clearly. Which windows cd do you have? It's a Windows XP, Vista, 7 or another installation CD? A Windows XP installation CD dosn't provide a cmd prompt. You have to build a PE. Boot a Vista or Windows 7 installation DVD and press F10 to get a cmd prompt.

Which command prompt do you expect? Press R to get to recovery console . Or press F10 at F6 message.

Not tested, try edit txtsetup.sif: don't load usbstor. Comment one line [InputDevicesSupport.Load] ;usbstor = usbstor.sys

sanjeev18 bai edit winnt.sif and remove unattended part. A basic winnt.sif [Data] MsDosInitiated=0 [UserData] ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" ComputerName=WINXP3 FullName="window xp 3" OrgName="Multimedia"

You are shure? Distributing non distributable files without manufacturer permission? http://www.boot-land.net/forums/index.php?showtopic=11982&st=9 As for core PE: Move directory \I386 to another 4 char name. And \Programs to \Programs. Boot a (RAM) edited setupldr.bin. As for multiboot part: include single parts to your multi boot loader Or if you have a lot of RAM, use a ISO RAM load approach http://ubcd4win.com/forum/index.php?showtopic=13764&view=findpost&p=76693 http://ubcd4win.com/forum/index.php?showtopic=14524&view=findpost&p=80078

Does HP SmartStart work at a virtual machine? A server maintenance CD may test hardware. Try a server maintenance CD at real hardware. Remember the flag file: /images/writeMBR.usb001 If you add grub4dos, store /images/SS850.iso and add /images/writeMBR.usb001 to server And boot from the server, then MBR is changed. That's unlikely to happen. So it's pretty unlikely a change at server in real life. Yes, MBR at USB.That's a one time change at USB MBR: you may remark the partnew line at menu.lst now: title HP SmartStart 8.50 x86 - fake isohybrid (hd0,3) ls /images/SS850.iso || find --set-root /images/SS850.iso #ls (hd0,0)/images/writeMBR.usb001 && partnew (hd0,3) 0x06 /images/SS850.iso root (hd0,3) kernel /system/vmlinuz media=usb rw root=/dev/ram0 ramdisk_size=399480 init=/bin/init loglevel=3 ide=nodma ide=noraid nopat pnpbios=off vga=791 noexec32=off nox2apic splash=silent showopts initrd /system/initrd.img Or with media=cdrom: title HP SmartStart 8.50 x86 - fake isohybrid (hd0,3) ls /images/SS850.iso || find --set-root /images/SS850.iso #ls (hd0,0)/images/writeMBR.usb001 && partnew (hd0,3) 0x06 /images/SS850.iso root (hd0,3) kernel /system/vmlinuz media=cdrom rw root=/dev/ram0 ramdisk_size=399480 init=/bin/init loglevel=3 ide=nodma ide=noraid nopat pnpbios=off vga=791 noexec32=off nox2apic splash=silent showopts initrd /system/initrd.img This depends on used hardware (removable or fixed) and operating system.Linux mount the partition usually. HP SmartStart may see another partition or not.

Can you clarify: which part does freeze? Open grub4dos command line and enter commands. At qemu 64 bit machine at 32 bit CPU: I get up to a round blue HP logo. Next a long delay or freeze: false hardware.

Disk full? Copy XPpSP3.ISO fails.

Integrate mass storage drivers, relating your netbook, into XP installation files first.

Read Post #1056 Write a error report to Security Essentials manufacturer: ask to fix the broken security application.

HP SmartStart dosn't support ISO file booting. A work around is required. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&prodNameId=344318&prodTypeId=18964&prodSeriesId=345557&swEnvOID=1005&taskId=135&swLang=13 Do you have a free partition entry at USB? You may map a continous ISO file /images/SS850.iso to a partition entry. This changes MBR permanent, be careful. As for safety there is a flag file /images/writeMBR.usb001 used. Create the flag file. Assumption: BIOS may USB boot drive to hd0. As fas as I remember HP does do this. At grub4dos menu.lst title HP SmartStart 8.50 x86 - fake isohybrid (hd0,3) \n\nWARNING: changes partition table hd0,3 ls /images/SS850.iso || find --set-root /images/SS850.iso ls (hd0,0)/images/writeMBR.usb001 && partnew (hd0,3) 0x06 /images/SS850.iso root (hd0,3) kernel /system/vmlinuz media=usb rw root=/dev/ram0 ramdisk_size=399480 init=/bin/init loglevel=3 ide=nodma ide=noraid nopat pnpbios=off vga=791 noexec32=off nox2apic splash=silent showopts initrd /system/initrd.img

What happens at fresher LPInstaller? Which local server?Mentioned message doesn't use a local sever. Read post 9. Edit file qa.ini, set you local iso file.

You have found them. It's this thread. Read first post.

Try Sandisk "LPInstaller.exe" http://www.hak5.org/forums/index.php?s=&showtopic=11236&view=findpost&p=114334

That's correct as for grub4dos.May be setupldr.bin dosn't find ntdetect.com. File system, file case and location is importand. How do you create the whole CD/DVD? Write some details.

Help, all Hell systems. The most USB trouble manufacturer. Write more details, which part fails? Remember to adjust ntdetect.com, compare FAQ. A BIOS may behave different at CD and USB boot. And a BIOS may map a missing floppy drive. Windows setup wait for floppy drive. Floppy is never detected, because there is no floppy drive, blank cursor for ever.

Early setup may hang at strange MBR partition table. "xp setup blank screen" is a general error. This happens at XP install from CD, XP install from USB and PE 1 boot. http://icrontic.com/forum/showthread.php?t=39459 http://forums.techguy.org/windows-xp/839435-solved-blank-screen-when-booting.html http://www.tomshardware.co.uk/forum/51554-35-windows-setup-blank-screen

Windows XP setup dosn't like strange MBR. Read some Linux or manufacturer recovery partition may interfere. Clean internal hard disk.

Thanks. Actual idea was a option to provide debug informations.Imagine ISO build failed at end user. Log some informations. If a error occour, open notepad. Ask the end user to post the log file. Hopefully the error source can be detected that way. That's pretty young Still a "Tales of Mystery and Imagination". Corrections happily appreciated. Option Explicit Const bootsect = "bootsect.bin" Dim fso, wsh, shl, fld, src, locpath, valid, bootable Dim MkisofsParams, wshExec, stdoutline, objDebugOutFile, LogFileName Set fso = CreateObject("Scripting.FileSystemObject") Set wsh = WScript.CreateObject("WScript.Shell") CheckStartMode locpath=Left(WScript.ScriptFullName,(Len(WScript.ScriptFullName)-Len(Wscript.ScriptName))) If Not fso.FileExists(locpath & "mkisofs.exe") Then MsgBox "mkiofs.exe missing", 16, "Error" 'vbOKOnly=0 vbCritical=16 WScript.Quit(1) End If valid=false bootable=false If WScript.Arguments.Count = 1 Then src=WScript.Arguments(0) ValidateSourcePath() End If If Not valid Then Set shl=CreateObject("Shell.Application") While Not valid Set fld=shl.BrowseForFolder(0, "Select source",16,17) '16=BIF_EDITBOX; 17=ssfDRIVES If fld Is Nothing Then WScript.Quit(1) src=fld.Self.Path Set fld=Nothing ValidateSourcePath() Wend Set shl=Nothing End If LogFileName = locpath & "mkisofs.log" Set objDebugOutFile = fso.CreateTextFile(LogFileName,True) objDebugOutFile.WriteLine("script " & WScript.ScriptFullName) objDebugOutFile.WriteLine("locpath: " & locpath) objDebugOutFile.WriteLine("source: " & src & vbCrLf) If bootable And Not fso.FileExists(locpath & "bootsect\" & bootsect) Then MsgBox "Boot sector missing (" & bootsect & ")", 16, "Error" WScript.Quit(1) End If MkisofsParams = "-iso-level 4 -joliet-long -duplicates-once -force-uppercase" & _ " -sysid ""Win32"" -V ""Windows"" -m thumbs.db" & _ " -o """ & src & ".iso""" & " """ & src & """ """ & locpath & "bootsect""" If bootable Then MkisofsParams = "-no-emul-boot -b " & bootsect & _ " -hide boot.catalog -hide " & bootsect & _ " -hide-joliet boot.catalog -hide-joliet " & bootsect & _ " " & MkisofsParams End If MkisofsParams = locpath & "mkisofs.exe " & MkisofsParams objDebugOutFile.WriteLine(locpath & MkisofsParams & vbCrLf) Wscript.Echo MkisofsParams & vbCrLf Set wshExec = wsh.Exec(MkisofsParams) Do While wshExec.Status = 0 stdoutline=wshExec.StdErr.Readline 'Wscript.StdOut.WriteLine stdoutline 'write to standard output Wscript.Echo stdoutline objDebugOutFile.WriteLine(stdoutline) 'write to file at the same time Loop objDebugOutFile.Close If wshExec.ExitCode <> 0 then 'Wscript.Echo vbCrLf & "ErrorCode: " & wshExec.ExitCode wsh.Run "notepad.exe " & LogFileName End If Sub ValidateSourcePath() If fso.FileExists(src) Then src=fso.GetParentFolderName(src) If Not fso.FolderExists(src) Then Exit Sub If fso.FolderExists(src & "\i386") Then valid=true bootable=true Else If MsgBox("The specified folder doesn't contain Windows XP" & chr(13) & chr(10) & "Create a data CD instead?", 36, "Warning") = 6 Then 'vbYesNo=4 vbQuestion=32 valid=true bootable=false End If End If End Sub ' http://ask.metafilter.com/79481/vbscript-printing-to-command-line Sub CheckStartMode Dim strStartExe ' Returns the running executable as upper case from the last \ symbol strStartExe = UCase( Mid( wscript.fullname, instrRev(wscript.fullname, "\") + 1 ) ) If Not strStartExe = "CSCRIPT.EXE" Then ' This wasn't launched with cscript.exe, so relaunch using cscript.exe explicitly! ' wscript.scriptfullname is the full path to the actual script wsh.Run "cscript.exe """ & wscript.scriptfullname & """" wscript.quit End If End Sub

Which particular machine gives the error? May be another member solved this already. I understand: this particular BIOS map a 16gb USB stick to a 1.44mb floppy drive. Windows setup use BIOS to access boot media. This fails at such mapping: biosinfo.inf not found. Almost all BIOS map a 16gb USB stick to a hard disk. Windows setup does work.