cdob

The "Maintenance and Service Guide Tablet PC TC1000" refers hard drives 40 GB 311240-001 30 GB 310668-001 The BIOS should detect the full capacity out of the box. Most likely there is another reason. Which adapter do you use? I would try another Compact Flash to IDE adapter. Unkonown Compact Flash to IDE adapter example http://www.daniel-boehmer.de/thinkpad-cf/

Do you use the driver from post #234? There is no file amd_sata.sys, nor at txtsetup.oem. There is a file ahcix86.sys. Which windows XP files do you use? Did you include any other massstorage drivers? Did you include a Vista/Windows 7 AMD AHCI driver?

Sorry, approach uses winload.exe for BIOS and UEFI. It's winload.efi at UEFI mode. And use Windows 7 x64 at UEFI mode, not x86 if %boot_mode%.==BIOS. call :add_PE \sources\b7PE_x86.wim "Windows 7 PE x86" call :add_PE \sources\b7PE_x64.wim "Windows 7 PE x64"

Yes, C is the default letter. No, not matter off. Given that C is already used, then another letter is used. Mentioned WinNTSetup does work: Windows 7 get letter D.

Which files are inside msdart CD?Does exist \boot\ \sources\boot.wim Bootmgr can load win7 and msdart. Rename \sources\boot.wim from msdart x86 and copy to win7 \sources\. Configure bcd to load this *.wim file. Repeat this to x64 *.wim file. Example \sources\boot_7PE.wim. Edit the 'call :add_PE' line to your needs. Add a second line for x64 .wim file. ADD_PE.cmd @ECHO OFFRem Add Windwos 7 PE to Windows 7 installset DVD_root=%~1if %DVD_root%.==. set DVD_root=DVDset boot_mode=BIOSset BCD_store=/store "%DVD_root%\boot\bcd"call :add_BCDBCDedit.exe %BCD_store% /enum allset boot_mode=UEFIset BCD_store=/store "%DVD_root%\efi\microsoft\boot\bcd"call :add_BCDoscdimg.exe -o -u2 -udfver102 -yo.\bootorder.txt -bootdata:2#p0,e,b"%DVD_root%\boot\etfsboot.com"#pEF,e,b"%DVD_root%\efi\microsoft\boot\efisys.bin" "%DVD_root%" AIO.ISOgoto :eof:add_BCD ===========================================================BCDedit.exe %BCD_store% /set {default} description "%boot_mode%: Windows Setup"rem Unify ramdisk settingsBCDedit.exe %BCD_store% /create {ramdiskoptions}BCDedit.exe %BCD_store% /set {ramdiskoptions} ramdisksdidevice bootBCDedit.exe %BCD_store% /set {ramdiskoptions} ramdisksdipath \boot\boot.sdiif %boot_mode%.==BIOS. call :add_PE \sources\b7PE_x86.wim "Windows 7 PE x86"call :add_PE \sources\b7PE_x64.wim "Windows 7 PE x64"goto :eof ==== create_BCD =============================================:add_PE ============================================================== for /f "tokens=1-3" %%a in ('BCDedit.exe %BCD_store% /create /application OSLOADER') do set guid=%%c BCDedit.exe %BCD_store% /set %guid% description "%boot_mode%: %~2" BCDedit.exe %BCD_store% /set %guid% osdevice ramdisk=[boot]%1,{ramdiskoptions} BCDedit.exe %BCD_store% /set %guid% device ramdisk=[boot]%1,{ramdiskoptions} BCDedit.exe %BCD_store% /set %guid% systemroot \windows if %boot_mode%.==BIOS. set winload=winload.exe if %boot_mode%.==UEFI. set winload=winload.efi BCDedit.exe %BCD_store% /set %guid% path \windows\system32\boot\%winload% BCDedit.exe %BCD_store% /set %guid% detecthal Yes BCDedit.exe %BCD_store% /set %guid% winpe Yes BCDedit.exe %BCD_store% /displayorder %guid% /addlastgoto :eof ==============================================================bootorder.txt boot\bcdboot\boot.sdiboot\bootfix.binboot\etfsboot.comboot\memtest.efiboot\memtest.exeboot\fonts\chs_boot.ttfboot\fonts\cht_boot.ttfboot\fonts\jpn_boot.ttfboot\fonts\kor_boot.ttfboot\fonts\wgl4_boot.ttfefi\microsoft\boot\bcdefi\microsoft\boot\efisys.binefi\microsoft\boot\efisys_noprompt.binsources\boot.wimsources\boot_7PE.wimsources\b7PE_x86.wimsources\b7PE_x64.wim

Try WinNTSetup http://www.msfn.org/board/topic/149612-winntsetup-v23/

Sorry, just ranting. No, it should work. And manufacturer supports Windows 2000 at this motherboard. Given different errors: I wonder about plain SP4 files or with integrated Update Rollup Pack.

A Intel motherboard with a ATI IXP 450 Southbridge. That's AMD hardware at a Intel motherboard. This is impossible and will fail Back then I used a AMD K6 CPU at a Intel chipset. Didn't you update the BIOS in the meantime? http://www.msfn.org/board/topic/169569-video-error-during-install-when-gui-is-started/#entry1058307 Do you get USB 2.0 speed at Windows? In addition there are another USB driver versions. http://www.msfn.org/board/topic/129829-usb-functional-patches-for-win2000-after-sp4-and-r1/ http://blogs.msdn.com/b/usbcoreblog/archive/2009/11/13/list-of-the-latest-usb-hotfixes-for-each-windows-version.aspx And remember there are PCI USB 2.0 NEC cards. May be there is a spare one in your technical trash bin.

Which hardware do you use? Machine, motherboard, USB port? Can you change BIOS USB emulation? Do you use a front USB port? Try another USB port.

XP USB install is not supported by manufacturer. This adds another level of complexity. Describe more detailed: how do you installed XP? Did textmode find a hard disk? Did textmode copy files to hard disk? Do you get a error message? Remember to press F8 to disable automatic restart. And try a install from a real CD too.

No, XP setupldr.bin doesn't support UDF. Use ISO9660 1988 Level 3 instead, a 5 GB file is possible. ImgBurn can do it. Move the big file to end of media. Bootable XP DVD above 4.7GB possible? http://www.msfn.org/board/topic/133537-bootable-xp-dvd-above-47gb-possible/

Go on. Try it.

Don't do this. Don't mix drivers with nLite. nLite dosn't support textmode name conflicts. Well, should work in that case, given equal *.sys driver files.

View your picture: do you read Southbridge 82801GB (ICH7/R) ? Try the first one a)

That's a ICH7. Read the first post here and read http://www.win-raid.com/t22f23-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-CD.html Try the textmode driver v11.2.0.1006 WHQL and the modified v11.2 RST driver.

Another idea: start with the 4 GB image. A fixed size VHD image is nice, It's almost a RAW image and is supported by a virtual machine, wimb created VHD_XP_Compact, thanks. http://www.911cd.net/forums//index.php?showtopic=25375 Use this to trim down the VHD image. No idea, if this support the unknown office version. If this fails, you may use the 4 GB image still.

Do you run bcdedit to adjust partition layout settings after image apply? Which error message do you get, if it dosn't boot? Run a bcdedit, post the output from the failed computer. Rename the file c:\boot\bcd first, 'run bcdboot c:\windows /s C:' next

Which computers do you use? Describe the hardware. Which computers list bootmgr error? Which bootmgr error do you get? Which image do you apply? Does this image contain a file \boot\bcd already? Do you use one hard disk or more hard disks? Are there any card readers? How do you run imagex? Do you boot a PE? How do you boot the computer Do you boot from CD/DVD, USB flash, USB hard disk, network,...?

Especial the burn engine is awesome, best in the world. And the build engine is good too: ImgBurn offers optimisation Enable the feature <Build><Optimise Duplicate Files>

There are different windows versions with different requirements. Which windows version do you like to use? Can you show a file list? Do you create hardlinks at hard disk? How do you prepare the ISO so far? Oscdimg Command-Line Options http://technet.microsoft.com/library/dd799243.aspx It's part of WAIK http://www.microsoft.com/download/details.aspx?id=5753 CDimage was first and Oscdimg next http://www.msfn.org/board/topic/33529-optimize-iso-limitation/ http://www.msfn.org/board/topic/107725-creating-vista-ultimate-boot-dvd-solved/ I like mkisofs still http://www.msfn.org/board/topic/56861-hardlink-on-cd-iso/

The DDO partition type 0x54 HDD connected at another XP machine with a IDE USB adapter. XP does mount the HDD, a virtual HDD is attached. The entire disk is shifted by 63 sectors and the first 63 sectors are hidden: The virtual HDD \\.\PhysicalDriveN sector 0 maps to real HDD sector 63 The partitions are mounted. Another hint http://reboot.pro/topic/18734-looking-for-a-way-to-detect-an-ide-drive-from-a-bootloader/ New game 3, HDD manufacturer independent approach: HDD sector 0 cleared. The truncated 32 GB HDD connected as primary master. XP installed to a 8 GB partition. A floppy image created, grub4dos included to boot code. a:\grldr added and a:\menu.lst title (hd0,0)/ntldrchainloader (hd0,0)/ntldrSeagate "DiscWizard Starter Edition 10" booted and a rescue DDO floppy created. Keep a Seagate HDD nearby, dosn't has to be connected... The existing bootsector is remapped and used later. Grub4dos added to HDD and menu.lst title load DDO map --mem /ddo.img (fd0) map --hook chainloader (fd0)+1 rootnoverify (fd0)The machine does boot Grub4dos loads the DDO from the floppy image. Next the DDO chainloads pervious boot sector code: grub4dos inside floppy image, this chainloads HDD ntldr XP does boot, the whole 40 GB HDD is available Further step: You may replace grub4dos inside floppy image, use a:\ntldr and a:\boot.ini instead. Added: include ntdetect.com and adjust pervious boot sector code too. Yes, it works.

What's a floppy? I'm lazy to dismount the flopy drive from another machine, no spare one available. Another HDD attached as primary master, the 32 GiB truncated HDD attached as secondary master now. Grub4dos installed to primary master MBR. Grub4dos does load: It's reported as 8 GB drive.partition type 0x54: compare section: 8.2 DM6:DDO http://www.tldp.org/HOWTO/Large-Disk-HOWTO-8.html cat --hex (hd1)63+1Yes, there is another MBR.Circumvent the DDO: map (hd0) (hd2)map (hd1)63+16434000 (hd0) The used XP partition is less than 8 GB, within available boundary. map --hookroot (hd0,0)chainloader /ntldrbootXP does boot. First 32 GB of HDD available.XP seems to shift 63 sectors given a partition type 0x54. With the DDO map (hd0) (hd1)map (hd1) (hd0)map --hookroot (hd0,0)root (hd0,0)chainloader +1XP does boot. The whole HDD is available. The HDD set to a 40 GB HDD:connected as primary master, configured as non at BIOS: Machine dosn't boot, BIOS hangs connected as secondary master, configured as non at BIOS: Machine dosn't boot, BIOS hangs @Roman78 Try the suggested steps.

Boot media CD-ROM drive at TX-P4 grldr as no emulation CD: CD not bootable NT default bootsect.bin edited to load grldr as no emulation CD: CD not bootable grub4dos 0.4.2 floppy image written as floppy emulation: grldr not found All three CD does boot at another system. A Isolinux and a BCDW boot CD does boot. Chainloading grldr.exe not tested so far. As for testing: A 40 GB Maxtor HDD truncated to 32 GB (66055248 sectors). And a Seagate HDD added too. Seagate DiskWizard 10 booted. DiskWizard does handle a non Seagate HDD, as long another Seagate HDD is available at system. (DiskWizard does refuse a single connected non Seagate HDD.) The DDO is written to the Maxtor HDD, a 8 GB partition created. The Seagate HDD disconnected. XP installed. Textmode offers a 40 GB HDD, installed to previous created 8 GB partition. The 40 GB is writeable and readable at installed XP. BartPE booted from CD (no DDO loaded): HDD is available, offline XP is writable. However first 32 GB is readable and writable only.

No, writing beyond the 32 GB fails actually: IO error Game lost: plain XP without a DDO is not possible.

New game 2nd: plain XP, without a DDO DiscWizard v10 list max sectors, even at a truncated 80 GB HDD. PTEDIT32 is available still ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/PTEDIT32.zip 1. Truncate the 80 GB HDD to 32 GB (Seagate DiscWizard or IBM Drive Fitness) Remember HDD max sectors 2. Connect the HDD to the DLOG HPC 5 as primary master with BIOS support 3. Install XP, create a partition less than 32 GB 4. run disk manager, create a second data partition: size fill up to 32 GB, don't format the volume 5. run ptedit32, recognice "Sectors Before" from second partition set "Sectors": calculate max sectors less sectors before 6. Reboot, format the volume 7. Enjoy a 80 GB HDD Be carefull: not fully tested