cdob

amd_sata.sys is a storport.sys child driver. That's supported at 2003 and up. http://msdn.microsoft.com/en-us/library/windows/hardware/ff567541(v=vs.85).aspx amd_sata.sys won't work in XP. Yes, it's confusing. http://sites.amd.com/us/game/downloads/Pages/integrated_xp-32.aspx#2 Information is misleading. The RAID driver does support AHCI too. Ignore the web page: do not use AHCI drivers at AHCI use RAID drivers at AHCI. Added: It's documented actually: 12-1_xp32-64_sb\$_OUTDIR\Packages\Drivers\SBDrv\SB7xx\AHCI_svr\XP\readme.rtf Strange: a driver at \xp\ directory matches 2003, but not XP.And amd_sata.inf .5.2 refers to 2003. That's 2003 only, not XP.It's a nLite error to include this driver to XP.

Keep original boot data. Use a additional device, map this to hd0. XP writes core boot data to this device. E.g. use a hard disk image file http://reboot.pro/15126/page__view__findpost__p__137793 http://reboot.pro/15126/page__view__findpost__p__143812

v06 major redesign One driver only - firadisk no need to include setup.exe in floppy image Driver firadisk is used within installation. And disabled at end of installation. A sample menu.lst is included. Usage examples: 1: simple case, friendly BIOS - try this first ISO contents read from USB disk, not loaded to RAM. 2: strange USB BIOS or hardware - adds a reboot if necessary ISO contents read from USB disk, not loaded to RAM. 3.map : small map RAM loaded boot files ISO image created by mkISO_RAMload_sort.cmd Loads textmode boot part to RAM, about 10-20mb data. This includes recovery console. Other files are read by windows drivers at USB 2.0 speed Prefer at USB1.x BIOS speed 3.dd: small dd RAM loaded boot files Uses dd to copy data. Lower speed, a fargmented ISO image possible. 4: RAM loaded install files ISO image created by mkISO_RAMload_sort.cmd Loads textmode boot and copy part to RAM Fastest approach at USB 2.0 BIOS speed 5: RAM load ISO image simple approach, use a existing ISO image

It's about ANSI and OEM codepages. CMD file uses ANSI codepage and command line uses OEM codepage. Adjust codepage. Try a example set CodePage=HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage FOR /F "tokens=1-2*" %%a IN ('%SystemRoot%\system32\reg.exe query "%CodePage%" /v "OEMCP"') DO (set OEMCP=%%c) FOR /F "tokens=1-2*" %%a IN ('%SystemRoot%\system32\reg.exe query "%CodePage%" /v "ACP"') DO (set ACP=%%c) echo current CodePage %SystemRoot%\system32\chcp.com dir c:\æøå echo set CodePage to %ACP% %SystemRoot%\system32\chcp.com %ACP% dir c:\æøå echo set CodePage to %OEMCP% %SystemRoot%\system32\chcp.com %OEMCP%

I don't use a A50M fusion. Does this match a A50M fusion? Currently driver supports However I doubt the RAID IDs at given machnie, a AHCI ID should match.

Read http://www.msfn.org/board/forum/157-install-windows-from-usb/

CQ43 Maintenance and Service Guide http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02950273/c02950273.pdf Chipset at AMD processor machines: AMD A50M fusion controller hub (FCH) Try

#119 Thanks for the head up.Any way to use remap hard disks only? Use a own firadisk.img, map a ISO, command run to remap drives and continue. E.g. map %myISO% (222) ... command %dir%/run remapHD root (222) chainloader /I386/SETUPLDR.BIN BTW: I'm looking forward to visit Fairy Meadow http://en.wikipedia.org/wiki/Fairy_Meadow_Nanga_Parbat But I doubt this year, hopefully next year. It's under construction. I've fun with different approaches and different BIOS. That's simple: integrate firadisk to ISO image. That's another approach. XP setup reads driver from both floppy drives. Try IMA at fd0 and dpms at fd1. But BIOS does matter too. May work at one BIOS and fail at the next. Two different floppy approach seems to work technically, but not reliable in real world.

Can you clarify? Do you like to boot Windows XP from a USB stick? Do you like to boot from a USB stick and install Windows XP to a internal hard disk? Did you lost the files or the USB stick?Is the USB stick available still? Did you changed removable bit in the past? Does Windows list USB stick as a fixed drive or a removable drive? Did you view both partitions after booting? Did you used a filter driver like cfadisk to enable second partition?

Can you change this setting? Use internal hard disk as first boot device. Press a hot key to boot from USB, e.g. F9, F11, F12.

Recovery console is integrated already: press F10 at F6 message.

As jaclaz indicated already: that's a strange revocery cd. True contents are unknown so far. No idea to set recovery procedure. Ask the creator Advent, If you like to follow this route. At the other hand, you may create a common known installation media. There are knwon working tools to add drivers to a installation media. Make a full file list with names, dates and size. Use either dir or ls. Compress the list and upload it.

How are disk builded? One 1.2 mm thick disc layer? Or two 0.6 mm thick disc layers glued together? http://en.wikipedia.org/wiki/CD-ROM http://en.wikipedia.org/wiki/DVD I wonder previous assumption: hard disk image and full installation files. Make a full file list with names, dates and size, either dir or ls. Compress the list and upload it. Read the ATIP. Most good manufacturer dosn't produce CD/DVD discs anymore.Read at a cdrinfo media section. http://www.cdrinfo.com/forum/tt.asp?forumid=56 http://www.cdrinfo.com/forum/tm.asp?m=141854

http://hothardware.com/cs/blogs/mrtg/archive/2009/03/09/mechanical-key-switch-keyboards-demystified.aspx

I'm confused: How do you make a verbatim copy? How much data holds the rescue DVD? How to write a full DVD to CD? Trust ImgBurn, distrust the media: destroy the media. ..by chance and may cause unpredictable errors in future. Distrust thir DVD+RW media in future.

Well, manufacturer release different driver versions, but use the same file name. A newer driver may abandon a old hardware. This causes file name conflicts. nlite dosn't support this. Add one mass storage driver per chipset manufacturer. This match certain hardware, but not all SATA and RAID drivers.

A G80-3000 uses individual key switches still and is available with three different types of confirmation: linear, soft or click pressure point http://www.cherry.de/cid/b2b_kabeltastaturen_G80-3000.htm? http://www.cherry.de/cid/b2b_kabeltastaturen_G80-3000.htm?rdeLocaleAttr=de&WT.mc_id=#Ausfuehrungen

Did you delete USB and DVD at device manger and boot again? That's a custom recocery media by design: A PE is bootted from DVD:\I386\ A application restores a hard disk image from DVD:\PRELOAD\ Remastering this requires editing the disk image files. No idea which application created this hard disk image, can be password protected in addition. However DVD:\I386DIST\ seems to contains XP installation files. What about install XP from single files? Delete directories iso/dvdrecorder/I386/ iso/dvdrecorder/PRELOAD/ rename iso/dvdrecorder/I386DIST/ I386 Follow imgburn XP installation guide to burn a CD/DVD. Remember slipstream SP3 requies a running XP. Try exising XP files first. Add SP2, SP3 and drivers to a addional directory \SP\

Mystery continues. Can you run title debug MCE2005.ISO map --mem /Inst/XP_Inst.ima (fd0) map --hook write --offset=0 (fd0)/setup/EMPTY512.LST \\XP\\ISO\\MCE2005.ISO\r\n;\r\n; cat (fd0)/setup/EMPTY512.LST pause I get What's your output?

Which ISOimage.ini file do you use inside floppy image? Which file size goes to this file? Write won't change file size.

Which grub4dos version do you use? Command does work here at 0.4.5c 2012-01-17 : cat does list \XP\ISO\MCE2005.ISO Write a report to grub4dos author. And add a ; in addition. write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\MCE2005.ISO\r\n;\r\n;But I doubt this solve described case. Added: Which ISOimage.ini file do you use inside floppy image? Which file size goes to this file? Write won't change file size.

XP support HD drives out of the box, this includes a SATA HD. But you may have to add driver for a mass storage CONTROLLER. Which mass storage controller drivers does include this?I miss a proper driver at this package. Which AHCI drivers did you include? Use a USB floppy drive. XP is historic nowadays.Try AMD AHCI drivers from KB922976 dosn't match XP. Added: AMD offers RAID drivers http://sites.amd.com/us/game/downloads/Pages/integrated_xp-32.aspx#3 This includes XP AHCI 12-1_xp32-64_raid.exe\$_OUTDIR\Packages\Drivers\SBDrv\SB8xx\RAID\XP\ahcix86.inf

Which windows contains file MCE2005.ISO? Strange: didn't this work at other versions so far? Try CR+LF: \r\n http://en.wikipedia.org/wiki/Newline write --offset=0 (fd0)/setup/ISOimage.ini \\ISO\\MCE2005.ISO\r\n;\r\n

There are different approaches. Use nlite to integrarte firadisk. Or use Or use another approach: Copy firadisk.sys and firadisk.inf to directory \I386\ Edit \I386\TXTSETUP.SIF [SourceDisksFiles] firadisk.sys = 1,,,,,,,4,0,0 firadisk.inf = 1,,,,,,,20,0,0 ;firadisk.inf edited: CopyFiles excluded: ;[FiraDiskDevice.NTx86] ;;CopyFiles=CopyFilesFiraDisk_x86 [BootBusExtenders.Load] firadisk = firadisk.sys [BootBusExtenders] FiraDisk = "FiraDisk Virtual Disk",files.none,firadisk Add a \I386\MIGRATE.INF [Version] Signature = "$Windows NT$" [Addreg] ;search ISO image HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso" ;#################################################################################### Edit \I386\HIVESYS.INF [AddReg] ;search ISO image HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso" ;#################################################################################### menu.lst title Setup Windows XP from ISO: \nfiradisk integrated in ISO image set myISO=/images/winsetup.iso #ilko_t http://www.msfn.org/board/topic/149675-install-xp-from-a-iso-file/page__view__findpost__p__988093 /boot/shifthd.bat find --set-root --devices=h %myISO% map %myISO% (222) map --hook root (222) chainloader (222)/I386/SETUPLDR.BIN This assumes a USB boot friendly BIOS. At a strange BIOS feel free to include USB settings from Post #58

7-zip to expand the gzipped file. Grub4dos does read gz compressed files. A strange USB BIOS. Certain Dell are famous. Can you list used hardware? False question. I've no idea about a "safer" approach. A additional code may cause a additional errors.A plain approach may be "safer", but fail at some machines. Plain firaddisk single USB boot will fail at half broken BIOS. These machines are seldom. Or the other way round: plain firaddisk single USB boot works at almost all machines.