cdob

Well, I don't pocess the hardware and have to guess. No step-by-step solution. Without manufacturer support, you have to find a solution yourself. The given thread: http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/General-XP-Downgrade-Guide-for-HP-Laptops/td-p/83267 refers "Model BELOW dv65xx and with AMD processor refer to dv6000Z drivers." Here http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en〈=en&lc=en&os=228&product=3224052#N301 Try this Chipset driver. How do you run nLite? 7-zip does expand HP sp33411.exe. Or try "32bit nForce LEGACY drivers v6.99 mod by Fernando" http://www.msfn.org/board/topic/51140-integration-of-nvidias-nforce-raid-and-ahci-drivers/ Yes, this is to be expected. I doubt strongly a Intel SATA AHCI driver at a AMD CPU motherboard.

Do you have a Windows 7 install DVD? There is no turion 64 x2 TL-50 sata drivers. A SATA device is connected to the chipset. A Quanta 30B7 refers to a nVidia nForce 410 http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/Tips-on-downgrading-dv6000-from-Vista-32-bit-to-XP/td-p/56525 XP drivers http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en〈=en&lc=en&os=228&product=3224052#N301 If I remember correctly, this chipset dosn't support AHCI features. Try IDE mode. There are Nvidia drivers anyway http://www.msfn.org/board/topic/51140-integration-of-nvidias-nforce-raid-and-ahci-drivers/

Which dv6000 do you use? Do you use a o dv6000T or o dv6000Z A AMD CPU refers often to a AMD chipset nowadays. http://www.msfn.org/board/topic/170936-amd-sb700-ahcichipset-driver/

Do you use Windows 7 x86 or x64? Yes, the JX-9600 manufual refers HP PCL 5 (Laserjet III series) @b-man Does your printer support PostScript? Then try the Windows 7 default Generic printer "MS Publisher Imagesetter" too.

That's a SB8xx southbridge at IDE mode. Which HardwareID refers to your AHCI mode? Could be PCI\VEN_1022&DEV_7801&CC_0106 or PCI\VEN_1022&DEV_7804&CC_0106 Did you adjust the HardwareID to ven_1022 ? Remember SB6xx and SB7xx ven_1002. Contrary SB8xx ven_1022 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1022&cc_0106] Which HardwareID did you used? Did you used the AHCI or IDE HardwareID ?

First I guess there is a XP backup...Brute force: Kids, don't do this at home: copy ahcix86.inf danger.inf, edit danger.inf [ATI]%NapaDesc%=Napa_Inst,PCI\VEN_1002%NapaDesc%=Napa_Inst,PCI\VEN_1022Be aware: this connects all ATI/AMD devices to ahcix86.If it's boot at AHCI mode, delete latest files %SystemRoot%\inf\oem*.* next. That's the files from danger.inf. And delete the file danger.inf. Windows PNP should ask to install AMD AHCI driver. Point to the file ahcix86.inf. Reboot again. Delete section [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1022]

Edit the inf file. However that's the last approach. The hardware availables another one: Read the manual: B. Configuring SATA controller mode in BIOS Setup "OnChip SATA Port4/5 Type" can be set different to other SATA Ports. Connect the HDD to SATA Port4/5. And set the BIOS to AHCI with SATA Port4/5 to IDE mode. Boot XP from the HDD in IDE mode still. Next install AHCI drivers. Goto BIOS and set SATA Port4/5 to AHCI mode.

Which BSOD do you get? Which IDE driver do you use currently? A AMD IDE driver may conflict with the AMD AHCI driver. Do you use Standard Dual Channel IDE Controller? If not, then replace the AMD driver to Standard Dual Channel IDE at device manager. And disable the AMD IDE driver in registry. Try the AMD SATA RAID/SATA AHCI Driver 3.1.1540.127 provided by Gigabyte.

No WAREZ support. Do not use XP_INST_v06 and a historic menu.lst example.Historic examples are not supported at XP_INST_v06. Read the other examples from XP_INST_v06 to get a idea.There are RAM load examples too. I assume sufficient RAM at a 64 bit OS. Read: the whole ISO image fits to RAM. Try XP_INST.gz from post #287 and title Setup Windows XP x64 from ISO \n5: RAM load ISO image - floppies=1set dir=/imagesset myISO=%dir%/XP64.ISOset fdIMA=%dir%/XP_INST.gzcat --length=0 %myISO% > nul || find --set-root --devices=hf %myISO%map --mem %fdIMA% (fd0)map --mem %fdIMA% (fd1)map --mem %myISO% (222)map --hook > nulcat --locatei="= firadisk32" --replace="= firadisk64" (fd1)/TXTSETUP.OEM > nul || echo error %fdIMA% file error..#uncomment to enable fixUSBcommand (fd1)/grub4dos/fixUSB64.bat %myISO%#chenall's ntbootcat --locate=###### --number=1 (fd1)/TXTSETUP.OEM > nul || call :error %fdIMA% file error..set offset=%?%set fira.opt=cdrom,vmem=find:%myISO%;write --offset=%offset% (fd1)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n;cat --skip=%offset% --locate=/ --replace=\\ (fd1)/TXTSETUP.OEMcommand (fd1)/grub4dos/shifthd.batroot (222)dd if=(fd1) of=(fd0)map --floppies=1chainloader (222)/I386/SETUPLDR.BIN || chainloader ()boot

Does all 7 machines fails at ? map --mem %fdIMA% (fd1)map --mem (md)0x6000+800 (fd0)Does all 7 machines require? map --mem %fdIMA% (fd1)map --mem %fdIMA% (fd0) No, it's not solved. It's a nice work around, if you don't adjust both virtual floppy drives. Yes, there are equal. Firadisk author created one file for both. Keep this files.

Why do you change this? What happens at suggested menu.lst?Which hardware (motherboard, BIOS) do you use? map --mem (md)0x6000+800 (fd0)map --hook > nuldd if=(fd1) of=(fd0) count=1This create a empty floppy fd0. Windows setup should read fd1 only.Seems to be a BIOS issue. If you use fd0, then adjust fd0 txtsetup.oem too.Insert before chainlader dd if=(fd1)/txtsetup.oem of=(fd0)/txtsetup.oem

Yes, that's true. Be aware: this requires a x86 UEFI: at some ATOM CPU this fails at a amd64 CPU

There are 64 bit FiraDisk drivers at new attached XP_Inst.gzDefault is x86 drivers still, works at XP x86 and 2003 x86. Set 64 bit drivers at menu.lst: cat --locatei="= firadisk32" --replace="= firadisk64" (fd1)/TXTSETUP.OEM title Windows XP x64#2: strange USB BIOS or hardwareset dir=/imagesset myISO=%dir%/XP64.isoecho %myISO%set fdIMA=%dir%/XP_Inst.gzcat --length=0 %myISO% > nul || find --set-root --devices=hf %myISO%map %myISO% (222)map --mem %fdIMA% (fd1)map --mem (md)0x6000+800 (fd0)map --hook > nuldd if=(fd1) of=(fd0) count=1cat --locatei="= firadisk32" --replace="= firadisk64" (fd1)/TXTSETUP.OEM > nul || echo error %fdIMA% file error..#uncomment to enable fixUSBcommand (fd1)/grub4dos/fixUSB64.bat %myISO%#use original firadisk.inf#cat --number=1 --locatei="firaedit.inf" --replace="firadisk.inf" (fd1)/TXTSETUP.OEM > nul#chenall's ntbootcat --locate=###### --number=1 (fd1)/TXTSETUP.OEM > nul || call :error %fdIMA% file error..set offset=%?%set fira.opt=cdrom,vmem=find:%myISO%;write --offset=%offset% (fd1)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n;cat --skip=%offset% --locate=/ --replace=\\ (fd1)/TXTSETUP.OEM#cat (fd1)/TXTSETUP.OEM#pausecommand (fd1)/grub4dos/shifthd.batroot (222)chainloader /I386/SETUPLDR.BIN || chainloader ()XP_INST.gz

Thanks for report. It's not supported. I'll investigate this.

As for a average end user it's pretty fine. Given a decent SSD, use it and ignore technical details. It runs smoothly in real world. No, it's fixing some previous glitches. No, not the SSD runs better at all. A special feature works better. Value this feature for daily work: random write operations are seldom at a average end user. A average end user won't recognise any change. You have to decide at Windows 7 with TRIM: it's worth to run Performance Optimizations at all? Why take the time, if there is no real benefit after?

There is a sample-menu.lst included, the 2nd example refers to "strange USB BIOS or hardware" Try this one. title Windows 2003#2: strange USB BIOS or hardwareset dir=/imagesset myISO=%dir%/2003.isoecho %myISO%set fdIMA=%dir%/XP_INST.gzcat --length=0 %myISO% > nul || find --set-root --devices=hf %myISO%map %myISO% (222)map --mem %fdIMA% (fd1)map --mem (md)0x6000+800 (fd0)map --hook > nuldd if=(fd1) of=(fd0) count=1#uncomment to enable fixUSBcommand (fd1)/grub4dos/fixUSB.bat %myISO%#use original firadisk.inf#cat --number=1 --locatei="firaedit.inf" --replace="firadisk.inf" (fd1)/TXTSETUP.OEM > nul#chenall's ntbootcat --locate=###### --number=1 (fd1)/TXTSETUP.OEM > nul || call :error %fdIMA% file error..set offset=%?%set fira.opt=cdrom,vmem=find:%myISO%;write --offset=%offset% (fd1)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n;cat --skip=%offset% --locate=/ --replace=\\ (fd1)/TXTSETUP.OEMcommand (fd1)/grub4dos/shifthd.batroot (222)chainloader /I386/SETUPLDR.BIN || chainloader ()Yes, use XP_INST.gz from 06 version, don't change the file.By the way: I'm remember Concordia still http://en.wikipedia.org/wiki/Concordia_(Karakoram) The most impressive place I visited so far.

I haven't done this. Did you integrate a 2003 setup.exe to XP_INST.IMA?

It's real time on demand. Run Performance Optimizations on demand, the software trims at real time next: runs some minutes Most likely the Magician Software crawls the NTFS MFT and calculates unoccupied blocks. And informs the SSD firmware: this blocks are free to use Yes, I think so. Contrary there are other user experiences http://www.anushand.com/2013/02/how-to-improve-your-samsung-840-series.html http://superuser.com/questions/620917/is-there-a-way-to-schedule-samsung-magician-ssd-optimization Performance Optimizations seems to be useful at Windows 7 too. I don't know what Performance Optimization does actually. Again: you may measure the difference, but won't recognise this at real work

The files at a SSD are major fragmented. Yes, this is good. Ignore this. I don't understand this. No OS can "fragment" the SSD internally. Only the SSD firmware can access the blocks inside the SSD. This is SSD firmware internally too. No OS is involved. It's OS independed. Yes, GC is active. TRIM is real time issue, if the OS supports TRIM: Windows 7 In addition you may TRIM on demand using the Magician Software: Windows XP and Windows 7 Real world advice: ignore TRIM theory. You may measure a difference, won't recognice one in real world. Use the SSD and be happy.

http://en.wikipedia.org/wiki/Trim_(computing) If you delte a file, Windows 7 informs the SSD about this. The relating blocks are free to use by the SSD firmware. If you delete a file at running XP and boot Windows 7 next: Windows 7 dosn't know about a previously delteted files and dosn't inform the SSD. The XP partition is not trimmed that way. Still at running Windows 7: if you delete a file at XP partition, this file space is trimmed. Yes, the drivers should work. The fun starts here.

Windows 7 TRIM the windows 7 partition. It won't TRIM the XP partition automatically. TRIM informs the SSD firmware a storage space is deleted. If you intent to TRIM the XP partition at Windows 7, use the Magican software too. Yes, and you won't recognise a difference in real world, if you don't TRIM manually the next months. The XP AHCI driver may work or fail at this hardware. Choose a hardware with XP chipset driver manufacturer support. Yes, no need to integrate drivers. Mixing driverpacks and nlite massstorage drivers are not supported and is asking for driver conflicts. Don't do this. Do this from the installed Windows 7. If it's hidden, you can't assign a letter.

Which hack do you refer to? As far as I know, there is no way to enable live running TRIM at XP. Given the Magician software depends on usage. I'm using Performance Optimization every couple of month. Yes, there is no need to update the driver atapi.sys at AHCI mode. However the chipset manufacturer dosn't provide XP AHCI drivers. You may try a modded driver package at own risk http://www.msfn.org/board/topic/107504-integration-of-intels-sata-ahci-and-raid-drivers/ At windows 7 diskpart: set the XP partition ID 7 to unhide this partition. Yes, both partitions are unhidden. And remove the windows 7 partition drive letter at running XP.

Congratulations. Which chipset do you use? There are supported chipset driver. http://www.samsung.com/global/business/semiconductor/samsungssd/downloads.html http://www.samsung.com/global/business/semiconductor/samsungssd/downloads/Samsung_Magician_421_Installation_Guide.pdf You may TRIM the SSD at XP. There is no need to do this at Windows 7, of course you are free to do so. XP IDE mode is supported too, given this condition Yes, don't hide, unhide or set ID at daily use. Which first bootmanger do you use finally? Ntldr or bootmgr? Bootmgr makes more sense in the future. http://support.microsoft.com/kb/100525/en-us Primary active partition is about 30 years old and valid still today. Some choices: Windows 7 partition active: copy ntldr, boot.ini, ntdetect.com and adjust \boot\bcd XP partiton partition active: add Windows 7 boot files and adjust partition boot code and adjust \boot\bcdCODE]bcdboot.exe %SystemDrive%\windows /s M: /v bootsect.exe /nt60 M: /force BCDedit.exe /create {ntldr} /d "Boot XP" rem BCDedit.exe /set {ntldr} device partition=D: BCDedit.exe /set {ntldr} device boot BCDedit.exe /set {ntldr} path \ntldr BCDedit.exe /displayorder {ntldr} /addlast

There are common used types and threre are manufacturer defined types. It's a grey area, in doubt I prefer the manufacturer definitions. http://msdn.microsoft.com/en-us/library/jj979618(v=winembedded.81).aspx At given quest both 17 and 27 works fine. Setup is aware of 27. Some OEM manufacturer use this as recovery partition. It depends what you like to do inside a running windows. 0x12, 0x17 hidden after boot, no letter assignable 0x27 hidden after boot, diskpart can asssign a letter nontheless Using XP I would choose a SSD manufactorer with a windows mainternance tool. I'm using Samsung SSD at XP. Yes, use 07 por a NTFS partition. Setting ID and active are written to MBR. Not the best idea at a SSD at each boot. How often do you reboot to other OS? May Windows 7 access the XP partition? The drive letter is removed at diskpart by default. Bootmgr / ntldr are sufficient at given request so far.

No, do NOT do this. A format overrides a disk nowadays. The SDD if full that way, this is to avoided. There is no need to set align 1024, it's proper aligned by default.