jaclaz

alexBB, take it easy, man , I am sure geezery only tried to help. Before going around accusing people to be criminals, it would be a good idea to think over it a little and check the history of posts of a member. The Elby program is actually quite good. If you want a good driver for .ISO images, try IMDISK, though NT/2K/XP/2003, it appears to work correctly under Vista: http://www.boot-land.net/forums/ImDisk-f59.html http://www.ltr-data.se/opencode.html#ImDisk I guess that you are the same alexBB that posted here: http://forum.winimage.com/viewtopic.php?t=3023 http://forum.winimage.com/viewtopic.php?t=3024 I am crosslinking them to here. jaclaz

Here is some info: http://www.msfn.org/board/Creating-WinPE-b...on-t106822.html Particularly this one should be what you are looking for: http://www.911cd.net/forums//index.php?showtopic=18480 An OLD related thread: http://www.msfn.org/board/index.php?showtopic=47773 jaclaz

Yep, the "proper" way is to use WINNT32.EXE with a slipstreamed install, but since RatPack actually asked for a workaround.... ...and usually workarounds and bypasses are not straight lines from A to B, they tend to go through C, D and E before finally getting to B from A.... jaclaz

Your best bet is TESTDISK: http://www.cgsecurity.org/wiki/TestDisk Usually in these cases it can rebuild the Partition Table. Otherwise, you can use a file recovery tool, like PHOTOREC or PCINSPECTOR: http://www.pcinspector.de/ jaclaz

Maybe the SOURCE files are in some way nonstandard. I mean whence they come from? An OEM release (DELL,HP, etc.)? Have they been modified in some way (slipstreaming, nlite, HFSLIP, etc.) ? Most probably it's the first error (WINNT.SIF error) that triggers a chain of errors. jaclaz

Workarounds: http://www.boot-land.net/forums/index.php?...ic=2254&hl= http://www.boot-land.net/forums/index.php?...ic=2362&hl= Some info is also here: http://www.boot-land.net/forums/index.php?...ic=2692&hl= jaclaz

SINGLE XP install from USB: http://www.msfn.org/board/index.php?showtopic=61384&hl= http://www.msfn.org/board/boot-install-USB...html&st=437 Since it uses grub4dos it should be easy to add a UBUNTU install, adding a second instance of XP install might be tricky and require some hexediting of hardcoded paths. jaclaz

Yep, you don't even need a Primary partition, you can boot from floppy or oter removable device (can also be used as a primitive but quite effective security measure if you do not want people fiddling with your PC): http://www.xxcopy.com/xxcopy33.htm jaclaz

Cannot answer your question, but as I see it this is not correct: There is NO need whatsoever for the partition to be Primary, nor Active, any NT based system can be as well installed on logical volumes inside Extended. As far as I know all the booting happens using "internal" names, like arcpaths and \\Hardiskx\ syntax, drive lettering is only used later for some Registry settings, automatic lettering can be overridden by migrate.inf. Check these for some info: http://www.msfn.org/board/index.php?showtopic=85729&hl= http://www.boot-land.net/forums/index.php?...ic=2425&hl= http://www.911cd.net/forums//index.php?showtopic=19663 (and links therein) jaclaz

Well, the idea is to find the VID and PID of the device via SOFTWARE, without being cruel to the poor little thing.... See these: http://www.911cd.net/forums//index.php?showtopic=15776 http://www.boot-land.net/forums/index.php?showtopic=1659 jaclaz

Version 1 is here (not really "hidden" ) : http://home.woh.rr.com/pombo/tools/ http://home.woh.rr.com/pombo/tools/ManualWindowsSetup1.zip Besides being compiled, version 2.0 coorected bugs of version 1.0, so, without TonyPE's support, you might need to directly correct them in the .wsh, if those bugs affect your particular setup. jaclaz

Maybe you might try LZ-DOS: http://dos.nm.ru/ It is said to be fully compatible with DOS 7.1. About compatibility of DR-DOS, I would say NO, see this: http://www.drdosprojects.de/cgi-bin/anyboa...;aO=1&iWz=0 Q&A #3. jaclaz

Yep, as said drive letters are NOT properly set. I mean, the SAME drive gets different drive letters depending on what you chose when booting. If you are OK with this, this is not a problem , but it is very easy to confuse a volume with another, thus saving data to one while thinking to be doing it on another one, on what I call "properly set" all drives and partitions should get the same letter no matter which OS you booted from. jaclaz

Or use diskless angel: http://www.disklessangel.com/ I guess it is the cheapest of the available COMMERCIAL solutions, and has virtually no limits as there are packages for 1, 2, 3 and 4 gigabyte sizes. Alternatively, and provided you are ALLOWED to use SERVER 2003 SP1+ files, and willing to be limited to 512 Megabytes, you can use euhenio's method: http://www.911cd.net/forums//index.php?sho...19056&st=29 Of course using tftp32.... jaclaz

@All FYI, I recently had the confirmation of my long time suspect that the "several passes" are only wasted time; even the man who began it all, Mr. Peter Guttmann, admits as much in his "revised edition" paper: http://www.forensicfocus.com/index.php?nam...opic&t=2065 The "revised edition" can be found here: http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html And here is an excerpt from it, the "Epilogue" (i.e. the newly added part): (emphasis is mine) jaclaz

NO, changing the BOOT.INI won't work by itself, as drive letters will NOT be properly set. For an explanation of the suggested changes to BOOT.INI see this: http://www.msfn.org/board/BOOTINI-hard-drive-t25365.html Drive letter assignment is dependent on Disk Signature (4 bytes in the MBR), see this: http://thestarman.pcministry.com/asm/mbr/Win2kmbr.htm You need to change the Disk Signature, using MBRfix: http://www.sysint.no/Nedlasting/MbrFix.htm http://www.sysint.no/Nedlasting/MbrFix.zip http://home.graffiti.net/jaclaz:graffiti.net/ http://home.graffiti.net/jaclaz:graffiti.n...X/mbrfix0.2.zip or MBRWiz: http://www.mbrwizard.com/ AND change the /DosDevices key in Registry to avoid possible "mixing" of the two drives: http://www.911cd.net/forums//index.php?showtopic=20094 http://www.911cd.net/forums//index.php?showtopic=19663 jaclaz

Up to version 1.x it is FREEWARE, versions 2.x are SHAREWARE, you can get both here: http://www.aplusfreeware.com/categories/mmedia/WinSnap.html A newish VERY SMALL PDF READER: http://blog.kowalczyk.info/software/sumatrapdf/ Plugin for BartPE by Joshua: http://www.911cd.net/forums//index.php?sho...c=20715&hl= jaclaz

You are missing a "basic" step. The .iso file IS the CD, to be more exact it is a CD IMAGE, you do not burn the .iso file to the CD, you burn it "on" the CD. Forget for one moment about Roxio, download the freeware IMGBURN: http://www.imgburn.com/ Select in it "write" mode: http://www.imgburn.com/index.php?act=screenshots#isowrite http://www.imgburn.com/index.php?act=guides "Visual" guide: http://forum.imgburn.com/index.php?showtopic=61 jaclaz

Check this thread too: http://www.911cd.net/forums//index.php?showtopic=18995 jaclaz

Yes, FYI check this: http://www.911cd.net/forums//index.php?showtopic=18480 jaclaz

In some occasions I saw this kind of errors when an "under-spec" or faulty cable was used, typically using 40 leads IDE cable on ATAPI 66/100/133 drives or using one of those removable HD trays that internally use 40 leads cables instead of the proper 80 leads ones. Replacing the faulty cable got rid of the error in Event Log. jaclaz

Happy about it, all's well that ends well. No need to thank me, I know how it could be having a wife that is NOT pleased. jaclaz

Interesting! I never thought that the clever filesystem driver from here: http://ashedel.chat.ru/fat32/ Could work on the System drive. FYI, there is no need whatsoever of installing Windows 2000, you just need the NTLDR and NTDETECT.COM from win2K or XP/2003, since the referenced page affirms that you can later delete the Wn2K install directory. The problem might still be the FAT16 to FAT32 conversion, since not everyone has a partition manager app that can do that, and I am not sure about freeware tools that can do it, best bet is probably using method #3 here: http://www.users.globalnet.co.uk/~jeacocke/fat16to.htm (since cvt.exe is a DOS app, it may run from a DOS bootdisk ) It seems like the ME version, strangely enough definitely works from DOS: http://www.mdgx.com/secrets.htm http://www.md4pc.com/questions/36.htm or this proggie here: http://www.unusualresearch.com/cvtfat32/cvtfat32.htm jaclaz

I am not sure I understand you, isn't this enough? : http://www.nliteos.com/ http://www.nliteos.com/guide/ jaclaz

You seem to be confusing "Autorun" with "BootCD", they are VERY different things. You simply CANNOT boot a XP from DVD, though you may be able to boot a PE (WinPE, BartPE, UBCD4WIN, etc,) or Windows XP SETUP (install) from a DVD. But this won't help you much anyway, since you cannot install a program, say Office, to a non-booted OS on the hard disk. Maybe what you need is a CD multibootloader with two choices : 1) Load XP SETUP 2) Load XP from hard disk and then access your autorun menu jaclaz