jaclaz

What is the BSOD STOP ERROR? Not by any chance 0x0000007b? jaclaz

Really I cannot say, I usually disable SFC/WFP and let it be disabled. But really it doesn't apply as I run Win2k. I wonder how it can work though. I mean, normally the SFC_OS.DLL checks the files listed in SFCFILES.DLL. If you hexedit adequately SFC_OS.DLL, it checks NOT the files in SFCFILES.DLL If you have an empty SFCFILES.DLL, the SFC_OS.DLL check the files listed in it i.e. zero files. The referenced post by fdv explains the above better: http://www.msfn.org/board/HFSLIP-Test-rele...279#entry492279 Now, if you re-enable the SFC_OS.DLL with an unmodified list of files (original SFCFILES.DLL), it will start re-checking the listed files, and if any has been modified or is missing it will pop-up asking you to insert the CD. jaclaz

I think that nlite uses the "empty" .dll trick, originally developed by Damian Bakowski and bettered by Fred De Vorck: http://www.vorck.com/windows/about.html http://www.msfn.org/board/Nlited-XP-post-i...3.html&st=6 http://www.msfn.org/board/enable-file-protection-t71256.html jaclaz

This might not be of ANY use for you, but since I stumbled upon it by chance, I am posting it so that it may be of use to aome other members with similar (but not SAME) problem: http://users.telenet.be/jbosman/poweroff/poweroff.htm jaclaz

Other than replacing a file completely (which is not desireable for boot.ini), I am uncertain about methods to edit a text file other than via a GUI.How can it be done via CMD file? Here: http://www.msfn.org/board/Hand-BOOTINI-t66101.html http://www.msfn.org/board/Hand-BOOTINI-t66101.html&st=15 NIRCMD is great, but remember: "jaclaz

Yep , that's why I stated it to be a bit off topic. However, in my experience both the Hitachi cfadisk.sys and Anton Bassov's dummydisk.sys filter drivers worked flawlessly under 2K and XP. There is also a Freeware app that can access (and thus partition/format) Removable devices under 2K/XP, Swissknife: http://www.compuapps.com/download/Swissknife/swissknife.htm Also, to identify a controller, you may want to use Chipgenius, that usually finds more info than other utilities: http://www.boot-land.net/forums/?showtopic=4661 (cannot say how useful this can be with SD cards and the like or if it will even run on Win98) In the same thread there are links to other similar utilities. jaclaz

Maybe you've got a wrong version. Try asking for help in the referenced thread Fernando 1 is a real expert on the matter, and has solved a number of problematic cases. jaclaz

This works in 98 only: http://www.cs.umd.edu/hcil/mid/ MacOSx has something: http://www.dualosx.com/dualosx_en.htm and Linux has MPX: http://wearables.unisa.edu.au/mpx/ so NT based systems appear the only ones where it doesn't work? Would the things referenced here: http://weblogs.asp.net/cfranklin/archive/2...2/21/77787.aspx (courtesy of the Wayback Machine): http://web.archive.org/web/20060219114740/...rcade/rawmouse/ be of use? jaclaz

Actually it will take care of everything: 1) writing a new bootsector (either to file or booted partition) 2) adding corresponding entry to BOOT.INI if needed Make sure to read and understand the syntax. jaclaz P.S.: you can check posts on it's forum, here: http://forum.winimage.com/viewforum.php?f=1 in case of doubts, or ask for help there. Guess who will probably reply?

Which BSOD STOP error you get? jaclaz

Sure it can, it's a driver like any other, point is whether it will work with your hardware. Here: http://www.911cd.net/forums//index.php?showtopic=19486 And this also might interest you: http://www.911cd.net/forums//index.php?showforum=43 Particularly: http://www.911cd.net/forums//index.php?showtopic=21867 jaclaz

I understand that due to the fact you are in a Commercial Environment you cannot use nlite, but the given thread: http://www.msfn.org/board/Integration-Inte...ta-t107504.html gives first the howto to have the right drivers and .inf files, and then suggests nlite as integration method, but there are others, most namely the good ol' method linked to by Nois3: http://www.msfn.org/board/Unattended-insta...ATA-t13173.html the UNATTENDED.TXT suggested by Intel, (you should read a bit here): http://www.msfn.org/board/Device-Drivers-f88.html the F6 Virtual Floppy method with grub4dos: http://www.911cd.net/forums//index.php?showtopic=20543 and probably a few more that I am unaware of or cannot recall. jaclaz

OT, but not much Both FAT16 and FAT32 have by default two copies of the FAT tables. The idea is/was that of having some means of recovery in case of something went wrong. In real world, the two FAT mostly resulted in generating errors about the two FATs not being identical. It is possible to make a FAT filesystem with just one FAT: http://advancemame.sourceforge.net/doc-makebootfat.html http://advancemame.sourceforge.net/boot-download.html http://www.911cd.net/forums//index.php?sho...13784&st=44 http://www1.mager.org/mkdosfs/ Again OT, these may be of interest also: http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm http://tokiwa.qee.jp/EN/Fat32Formatter/ jaclaz

Perspiration? About this: http://support.microsoft.com/?id=303013 the pre-SP1 48 bit LBA support is EXPERIMENTAL, I wouldn't trust it, as it can corrupt other filestystems. Maybe, by disabling SFC/WFP (in SP0 it can be done by a Registry key), you could somehow "force" the SP1 ATAPI.SYS to work in SP0. What I would try first would be UNIATA: http://alter.org.ua/en/soft/win/uni_ata/ jaclaz

You mean "menu user friendly" or "menu maker friendly"? Does AeroStudio suits you? http://www.boot-land.net/forums/index.php?showforum=72 jaclaz

...or using migrate.inf... ...or modifying setupreg.hiv... jaclaz

Well, NO. The percent sign is the reserved character used to indicate a variable.... There are usually two ways to "escape" special characters, either "doubling" them like in "&&" or using the caret, like in "^&", (I presume that the second may work in this case) but the only way to know if either work would be to test them. jaclaz

Is your controller an INTEL SATA? If yes, looky here: http://www.msfn.org/board/Integration-Inte...ta-t107504.html jaclaz

No Prob. If needed, ask for help in there, Fernando 1 has solved a number of similar problems. jaclaz

Try the other way round. Make a small (less than 2 Gb, possibly less than one Gb) Primary partition, FAT16 Make an extended partition and inside it as many Logical volumes you need, to one of which you will install XP. Install XP. Get bootpart from here: http://www.winimage.com/bootpart.htm Create a bootsector for Win98. (and add an entry in BOOT.INI) with: BOOTPART WIN98 C:\BOOTSECT.W98 "Windows 98" Copy to the FAT16 drive IO.SYS, MSDOS.SYS, and COMMAND.COM Verify that you can boot to DOS (choosing "Windows 98"). Install Win98 normally. When you reboot you should get the Windows 98 (and not any way to run XP) Run Bootpart again: BOOTPART WINXP BOOT:C: to restore a bootsector invoking NTLDR. Reboot and you should have a choice between XP and Windows 98, both working. jaclaz

Nothing, it was just an attempt to explain why your key (that worked before) does not work: it shouldn't be related to SP level, but rather to versions. By mixing files, versions and SP's, you are not having: a SP0 build, you have, no offence intended , a "mess". What I would do if I were you would be: 1) check the files you have from your "original" SP0 with the ones i the lists linked here: http://www.msfn.org/board/XP-Professional-....html&st=19 2) put aside for the moment nlite and try another of the available options: a. slipstream directly (there are hundreds of tutorials to do so): http://www.winsupersite.com/showcase/windo..._slipstream.asp http://www.magiciso.com/FAQ/FAQ0004.htm http://www.5starsupport.com/tutorial/xp-recovery-cd.htm b. use HFSLIP: http://www.msfn.org/board/HFSLIP-f129.html c. use autostreamer: http://www.simplyguides.net/guides/using_a...ostreamer.shtml jaclaz

By default the "separator" in command line and batches is the "space", thus yes, a program that shoud be called as: will not interpret properly a command line like: as: 1st parameter=param1 2nd parameter=para 3rd parameter=m2 4th parameter=param3 By placing quotes around "para m2" you will obtain: 1st parameter=param1 2nd parameter=para m2 3rd parameter=param3 so with "normal" characters everything will be allright, but if a "reserved" character is used like %&<>=|^ to list a few, putting the two (or three) words between quotes may not be enough. jaclaz

It is possible that the problem is not in "more than one word" but rather in the use of the "&" sign, which is a reserved character. If the quotes do not work, you can try "escaping" the character, using && instead. jaclaz

Partition Magic cannot "repair" anything: http://www.msfn.org/board/Partition-Table-Errors-t65337.html Use TESTDISK: http://www.cgsecurity.org/wiki/TestDisk to check the partitions, though from what you write it seems more like a filesystem problem, possibly not fixable, if not by running CHKDISK. Before that, you should image the partition (just in case). And you may also want to try PHOTOREC (it comes with TESTDISK) to recover the files. jaclaz

@jetman Yes, but use the latest Winbuilder. The UXP combines a "FULL" install with a LiveXP, which is a self standing project capable of replacing a normal BartPE build. Particularly LiveXP has been proved to work for Winnt32.exe use. Do read these: http://www.boot-land.net/forums/?showtopic=4111 http://www.boot-land.net/forums/index.php?showtopic=5306 jaclaz