cdob

Let's investigate: How much RAM do you use? Create a file list from ISO image: isoinfo.exe -l -i XP_RAM.ISO > iso_list.txtIsoinfo is part of cdrtools package, as mkisofs. Can you upload ramboot.lst, sort.txt and iso_list.txt ?

Can you clarify some parts: Which windows files did you used? Do you use a OEM version? Did you slipstream a SP? How do you slipstreams? Did you changed windows files in addition? Did you edited, added or deleted a file? Which menu.lst do you use? Does RAM loaded ISO image contain a file RAMBOOT.LST? Which contents does contain file RAMBOOT.LST? How much RAM does computer hold?Sorry, there is a issue with relative path. Try full path MkISO_RAMload_sort.cmd C:\INST\XP_RAM

I doubt this.The file C:\INST\XP_RAM\bootsect.bin is missing. Remember case is importand: bootsect.bin is not BOOTSECT.BIN. And read the warning: XP_RAM\I386\txtsetp.sif not found. No sort file created. Read ISO image won't be sorted. Why do you use a sorted image at all? Can't you use the whole image?

@sh770 The source dir does containt the windows installation files. Create a directory C:\INST\XP_RAM\ Copy all files and directories from your windows installation CD to hard disk C:\INST\XP_RAM\ Extract the Boot Image file to C:\INST\XP_RAM\bootsect.bin. Case is importand. http://www.nu2.nu/bbie/ Copy mkISO_RAMload_sort.cmd to C:\INST\. mkISO_RAMload_sort.cmd Copy files to C:\INST\. In addition a windows default file find.exe is expected at path. Open a command prompt and run cd /d C:\INST MkISO_RAMload_sort.cmd XP_RAM @daddy_fizz No, I don't know a simplier methods to make a sorted ISO. Which errors do you get? @all To clarify: a sorted ISO file is optional.

@TYHK99 What's your experience with: Uppercase windows files at hard disk first: filecase.exe http://www.stevemiller.net/apps/ Use file system ISO9660:1999 and extension Rock Ridge without permissions. Don't use Joliet. mkisofs -iso-level 4 -r Use a boot loader and chainload setupldr.bin.

Set EnableBigLba mode: http://support.microsoft.com/kb/305098/

Read the FAQ again. Try the mentioned ntdetect.com

Read Q3

http://www.hobeanu.com/blog/bypassing-file-system-security-in-windows/

Choose a file system supporting your file name length. It's always a pleasure if recommendations are ignored. http://www.911cd.net/forums//index.php?s=&showtopic=23716&view=findpost&p=162200

Did you copy file to system32\drivers\ folder?

Enter BIOS and set the previous setting.

You don't update driver in device manager. Save the reg file code to a file. Import the reg file. Copy iastor.sys to %SystemRoot%\system32\driver. Reboot, goto BIOS, set AHCI, reboot. Ignore IMSM_PRE.inf so far.

Which hardware do you use? Does BIOS approach SD card as a hard disk? Did you tried generic PE boot? http://technet.microsoft.com/en-us/library/cc766092(WS.10).aspx Which windows driver is used at SD reader? Does your windows use sdbus.sys, sffdisk.sys and sffp_sd.sys? Did you apply KB976092? http://support.microsoft.com/kb/976092/

Yes, pci#ven_8086&cc_0106 refers to ICH7 too. Actually this refers to all Intel AHCI hardware.

Ignore the PE part. Your BIOS may use another name. Which nane does your BIOS use currently? Remember the The master boot record dosn't set AHCI. Ignore this.I doubt restoring a image include drivers. Old image won't boot. The link to the correct iastor.sys file was named already. Adding AHCI support to registry is a simple reg tweak too: just import a reg file. Lenovo offers a install.cmd to post install AHCI drivers. http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70477 Adjust IMSM_PRE.inf, add CriticalDeviceDatabase\pci#ven_8086&cc_0106.

The Service part load the driver. And the CriticalDeviceDatabase line points to iastor.sys. Copy and paste text, save to a iastor.reg. Import the reg file.http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=17883 Get a compressed file f6flpy3289.zip. Extract the file iastor.sys. Copy iastor.sys to %SystemRoot%\system32\drivers. Reboot. Goto BIOS, set AHCI. Boot to windows. Driver are added at basic settings. PNP ask for full installation, apply previous downloaded files. IDE emulation booting is possible still.Goto BIOS, set IDE emualtion and boot to windows. That's another approach: boot to a PE first.Current Windows is loaded from CD or USB. Read your working windows is offline. Insert the driver to the offline windows, the drive itself has to be online. I prefer fix_hdc myself. http://www.911cd.net/forums//index.php?showtopic=20464

No, there is no space. Sorry forum software display funny.

Well, one single yep is confusing to four questions. Thanks for clarifing. Ok, this clarify some parts. The etc. is the missing part. Can you name some examples again? ftp://ftp.microsoft.com/developr/drg/Multimedia/Joliet/Joliet-RTF.rtf A Windows 95 B CD use ISO9660 and Joliet here. No idea about a older version. Sorry could not resist: I consider Joliet a waste of space still. Contrary this should result a readable DVD in your case. Go ahead.

Compare post #213 Use the mentioned registry settings, but copy a iastor.sys relating to your hardware.

Can you post text examples: longest full path name: directory filename with extension deepest directory file, again as full path strangest unicode name, again as full path No, I don't know. The mentioned UDF reader was a freeware part of DirectCD. The reader may work at Windows 95 or fail. And read a ImgBurn UDF or fail. Try and report the result.

Yep. Apparently I only need Joliet Joliet dosn't support requirements.Joliet specification allows 64 chars PathChars. You may use 110 chars at own risk. Can you name some examples? Which directory and file names goes to DVD? Back then there was UDF reader for packet writing software.'Adaptec UDF Reader Driver 5.1.1.213' should work at Windows 95.

A different approach: don't use winnt32.exe. Follow flyakite's guide and ignore flyakite's guide. Create a directory XP32 Copy the directory I386 to XP32\I386 Create win51* flag files at root and at XP32 Copy files setupldr.bin, txtsetup.sif and ntdetect.com to XP32 Example layout: Edit setupldr.bin, change I386 to XP32 Edit txtsetup.sif, adjust SetupSourcePath and create BootPath: [SetupData] SetupSourcePath = "\XP32\" BootPath = \XP32\I386\ Configure your multi boot loader to launch file XP32\SETUPLDR.BIN. Chainload setupldr.bin. Or use a Boot Sector file: change I386 to XP32.

Uppercase required files, there are applications to do this. There is no need to rename a long name to 8.3 name.

CDFS does support file systems ISO9660 and Joliet. A bridge with ISO9660 and Joliet is readable at Win95. I consider UDF and Joliet a waste of space. And prefer ISO9660 names only.