jaclaz

"Say" port to Win32 (sort of): http://krolik.net/post/Say-exe-a-simple-co...or-Windows.aspx jaclaz

The problem might rely with Service Pack files (you need the SAME SP level as your installed OS), and with updates. All "personal" data and settings should remain untouched. Do read THOROUGHFULLY this (though it is XP related, same should apply to Server 2003): http://www.michaelstevenstech.com/XPrepairinstall.htm In ANY case, do make a full image of the system "as is", just in case. jaclaz

Well, not so easy. I have full faith on the power of grub4dos dd command, but alas not yet enough on grub4dos scripting language. You may have a "strange" BOOT.INI already on the target machine. See the example posted here: http://www.msfn.org/board/How-to-boot-inst...html&st=244 Are you positive that you can find a way (entirely in grub4dos) to detect the position of z, both here: and here: And later read the z value, calculate the z-1 value and write it in both places? jaclaz

Just for fun , and for future memory . The \ (backslash) trick works nicely in 7-zip filemanager too. Now a nice one (directory originally named fd - as acronym for fake directory): C:\testdirtilde>dir Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.25 <DIR> . 16/03/2009 16.25 <DIR> .. 16/03/2009 15.59 <DIR> fd 0 File 0 byte 3 Directory 290.000.093.184 byte disponibili C:\testdirtilde>dir /x Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.25 <DIR> . 16/03/2009 16.25 <DIR> .. 16/03/2009 15.59 <DIR> fd 0 File 0 byte 3 Directory 290.000.093.184 byte disponibili In 7-zip rename fd to ALT+0160..\ (meaning keep pressed ALT key, tap 0160 on numeric keyboard, than a DOT, than another DOT than a BACKSLASH): C:\testdirtilde>dir Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.30 <DIR> . 16/03/2009 16.30 <DIR> .. 16/03/2009 15.59 <DIR> .. 0 File 0 byte 3 Directory 290.000.027.648 byte disponibili C:\testdirtilde>dir /x Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.30 <DIR> . 16/03/2009 16.30 <DIR> .. 16/03/2009 15.59 <DIR> 71E7~1 .. 0 File 0 byte 3 Directory 290.000.027.648 byte disponibili C:\testdirtilde>cd 71e7~1 C:\testdirtilde\71E7~1> Folder is "invalid" in explorer and practically inaccessible from command line too, unless you use "the dir /x name". Works allright in 7-zip, though it is "strange" to see two seemingly "double dot " named directories.... You can do the same with SPACE DOT DOT BACKSLASH, the name will be 71E3~1 And now the nice part: After having renamed a directory to SPACE DOT DOT BACKSLASH, make another one, and rename it to ALT+160 DOT DOT BACKSLASH (same as before), it should get 71E7~1 as before, right? WRONG! This one will get just one DOT: C:\testdirtilde>dir Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.46 <DIR> . 16/03/2009 16.46 <DIR> .. 16/03/2009 15.59 <DIR> .. 16/03/2009 16.46 <DIR> . 0 File 0 byte 4 Directory 289.999.880.192 byte disponibili C:\testdirtilde>dir /x Il volume nell'unità C non ha etichetta. Numero di serie del volume: C08C-CFD9 Directory di C:\testdirtilde 16/03/2009 16.46 <DIR> . 16/03/2009 16.46 <DIR> .. 16/03/2009 15.59 <DIR> 71E3~1 .. 16/03/2009 16.46 <DIR> E20A~1 . 0 File 0 byte 4 Directory 289.999.880.192 byte disponibili and E20A~1 Pretty much unuseful..... but maybe can come handy for something.... B) jaclaz

Sure, as well as the old WINNT.EXE from DOS, but what would be the fun if we don't look and hopefully find new ways? jaclaz

Happy problem is solved. jaclaz

Maybe you were thinking about this one: http://downloads.zdnet.com/abstract.aspx?docid=744749 Homepage is here: http://www.dkpcode.com/html/downloads.html#DKHardDrive-Light Though ZDnet says: Developer says: jaclaz

It seems like a problem with the actual CD booting. Are the DVD's ATA or SATA? If SATA double check BIOS settings: http://www.computing.net/answers/hardware/...rive/51227.html You may also want to try disconnecting (temporarily) one of the two DVD's. jaclaz

I am starting to maybe understand. For the "casual" onlooker, this thread needs to be read together with this one too: http://www.msfn.org/board/index.php?showtopic=130828&hl= Still I have quite a few questions: What is the reason of the "abnormal" directory name? I mean, if you make a "normal" directory named "XPINSTALL" won't it be accessed by it's short name XP~1? Would this work with any filesystem or only on FAT? Can't we use a "fixed 4 character" and "normal" directory? I mean $WIN_NT$.~BT is 12 characters, why cannot we have (say) 1234\56789AB or 1\23456789AB or whatever "in the middle"? As well, once we have decided that we "need" 4 characters for the "base" directory name, can we, as txtsetup.sif is 12 characters as well, 1234\txsetup (with no extension?) or is the .sif extension needed? Same for ntdetect.com that could become 1234\ntdtect Same for bootfont.bin that could become 1234\bootfnt Same for boot.ini that could become 1234\ini What is the reason to change the name of menu.lst to "me"? It is not invoked by any of the NT files.... The above said, why do we need the "further" \I386? I mean, can we have INSTEAD of these: these: I hope to have not flooded you too much with all these questions , just trying to understand how to stretch to the maximum extents the "limits" of this renaming solution.... jaclaz

Well, it won't work. However that's the additional parameter you are giving to mkbtiso.bat, which will result in correspondent mkisofs commands: : *** File system options set fs_options= if "%1" == "-u" set fs_options=-N -d -D -no-iso-translate -relaxed-filenames -J -joliet-long -udf if "%1" == "-j" set fs_options=-N -d -D -no-iso-translate -relaxed-filenames -J -joliet-long if "%1" == "-l" set fs_options=-N -d -D -no-iso-translate -relaxed-filenames -max-iso9660-filenames -allow-multidot -allow-leading-dots -allow-lowercase if "%1" == "-lu" set fs_options=-N -d -D -no-iso-translate -relaxed-filenames -max-iso9660-filenames -allow-multidot -allow-leading-dots if "%1" == "-s" set fs_options=-N -d -D -no-iso-translate -relaxed-filenames if "%1" == "-v2" set fs_options=-iso-level 4 if "%1" == "-v2u" set fs_options=-iso-level 4 -force-uppercase : -N, -omit-version-number Omit version number from ISO9660 filename (violates ISO9660) : -d, -omit-period Omit trailing periods from filenames (violates ISO9660) : -D, -disable-deep-relocation Disable deep directory relocation (violates ISO9660) : -no-iso-translate Do not translate illegal ISO characters '~', '-' and '#' (violates ISO9660) : -relaxed-filenames Allow 7 bit ASCII except lower case characters (violates ISO9660) : -max-iso9660-filenames Allow 37 character filenames for ISO9660 names (violates ISO9660) : -allow-multidot Allow more than one dot in filenames (e.g. .tar.gz) (violates ISO9660) : -L, -allow-leading-dots Allow ISO9660 filenames to start with '.' (violates ISO9660) : -allow-lowercase Allow lower case characters in addition to the current character set (violates ISO9660) : -force-uppercase Do not allow lower case characters Thus, you can try INSTEAD of -j the -v2u one, or as said use directly mkisofs with the command line in the given link. jaclaz

And/or check these: http://www.911cd.net/forums//index.php?showtopic=16381 http://www.911cd.net/forums//index.php?showtopic=19109 Where you may find some ideas/tricks for the opposite thing. And also have a look at this: http://www.pcdecrapifier.com/home (again NOT what you asked for, but something that may be used as reference) jaclaz

You are running mkisofs with some "not appropriate" command line parameters. Please post the command line you are using or try with the one here: http://www.911cd.net/forums//index.php?sho...22726&st=13 You seem like not using "isolevel 4" jaclaz

Not really. As far as you get the RIGHT drive letters in the WINNT32.EXE parameters I cannot see how the running of WINNT32.EXE may affect the running system. But of course having a backup is always recommended. I was thinking, that although it might be really SLOW, you could setup in your Vista PC a Qemu VM, and then use the \\PHYSICALDRIVEn connection: http://www.msfn.org/board/Adding-QEMU-func...sb-t112746.html booting the VM from a PE CD of some kind and running the WINNT32.EXE to install the XP on the external drive. Or possibly, with the above setup, you should be able to use this method: http://www.msfn.org/board/index.php?showtopic=121446 jaclaz

Sorry I did not explain myself, or possibly haven't understood fully your report. If I get it right, this: This results in a directory XPLS containing the previous contents of the $WIN_NT$.~BT one plus the two files migrate.inf and winnt.sif. Than the contents of $WIN_NT$.~LS are moved to \XPLS ( or \XPLS\I386)? Can you simply attach a DIR /S of your modified stick, so that I can fully understand the directory structure and which files are where? I was presuming that your tests are made with the (right or wrong ) idea of putting the whole structure under a single directory (\XPLS) as to not "clutter" the ROOT of the stick/HD partition. What I am trying to understand is if we can somehow (through a batch for example) create a single directory (like \XPLS) instead of two (\XPLS and \XPLS\I386) and whether we can copy files to it/them directly from the \I386 directory of source CD. Or am I alltogether missing the point? Not really. rdummy.sys is to make a HD seen as "Removable" as opposed to "Fixed" once the GUI is up and running. During initial text mode part of setup, first active partition on first hard disk (read booted USB device) will get C:\ unless a migrate.inf (or some other unknown trick) is used, this will happen long before rdummy.sys gets "into play". jaclaz

I may add that however, grub4dos dd should be able to change a single byte even on a NTFS filesystem with no problems, haven't tested it, but from the grub4dos readme: should mean that it is possible that a problem happens, not necessarily that it will happen. The difficult part would be to tell it WHICH byte to change, i.e. somehow scripting the feature, both finding the "address" that needs to be changed and the right "value" to write. The "z-1" concept was devised to work on "ANY" setup : http://www.msfn.org/board/How-to-boot-inst...html&st=240 and following. jaclaz

Very interesting. This should mean that we could (instead of using \XPLS\I386) using directly \I386, and thus just by changing two files be able to copy the \I386 folder from Cd, right? The migrate.inf, as far as I can say, will be needed anyway (or it must be replaced with "something else"), it's the only way to prevent the USB stick (or Hard Disk) from becoming "C:\" in the install. I am not sure to have understood your report on the linked thread. Could you try expanding on it? jaclaz

It seems like a similar thingy for the Win9x/Me family is VERY diffcult to find. I was able to find a few, but all for the NT/2K/XP family. BUT B) : Here are a couple for "pure DOS": http://cd.textfiles.com/maxx/tothemaxsw/DISK/FILES.BBS DRVELD10.ZIP On-screen drive LED http://cd.textfiles.com/maxx/tothemaxsw/DISK/ http://cd.textfiles.com/maxx/tothemaxsw/DISK/DRVELD10.ZIP http://cd.textfiles.com/drsharewaregold/utility1/files.bbs KDL.ZIP TSR BLINKS NUMLOCK LIGHT AT DISK ACCESS http://cd.textfiles.com/drsharewaregold/utility1/ http://cd.textfiles.com/drsharewaregold/utility1/kdl.zip And here is a Win95 one , cannot say whether it would work on 98/Me : http://cd.textfiles.com/mediadepot/MENU/DIRLISTS/DIR41. hdled.zip 545758 13-09-96 Hard Disk LED simulates a hard disk light | that flashes every time there's a disk | activity. Hard Disk LED appears on the | Windows 95 task bar and flashes every time | the system accesses physical, direct access | devices (ie. your hard drives). http://cd.textfiles.com/mediadepot/FILES/41/?N=D http://cd.textfiles.com/mediadepot/FILES/41/HDLED.ZIP Unfortunately Shareware, will disactivate after 30 minutes.... A more recent version is here : http://hdled.home.comcast.net/~hdled/ reported as working for both 98 and Me, but the e-mail at attbi.com should mean that the thingy is "on it's own". jaclaz

From an authorized Microsoft site or dealer, or just a torrent or whatever WAREZ site? The distinction is not so subtle, please review Rules: http://www.msfn.org/board/index.php?showtopic=18408 before providing an answer..... jaclaz

A couple of notes related to "added" D paragraph : Please note that FDISK /MBR only replaces the MBR CODE (with the "default" Win9x one). It does NOTHING if the Virus or whatever has corrupted the MBR DATA. It is always a good idea to have (possibly on the same "emergency floppy" a backup of the complete MBR. If you don't have it, your only way out (possibly) is the use of TESTDISK: http://www.cgsecurity.org/wiki/TestDisk to re-build the MBR DATA It is unclear/undocumented if there is any advantage (or drawback) on a dual boot system to have the Win9x MBR CODE or the 2K/XP/2003 one. Not really. :whistling: If you already have an entry for BOOTSECT.W98 in your BOOT.INI you can simply run: BOOTPART WIN98 C:\BOOTSECT.W98 a new bootsector will be created, but NO entry will be added to BOOT.INI. Of course you need to use the SAME "BOOTSECT.W98" name for the "old" and the "new" bootsector. jaclaz

Should be this one: http://www.pcguide.com/ref/hdd/bios/size.htm http://www.pcguide.com/ref/hdd/bios/sizeGB315-c.html Or is it this one : http://www.pcguide.com/ref/hdd/bios/sizeGB30-c.html jaclaz

OK, I completely missed the point, let's see if I have understood it now. You don't want to install the XP on the USB drive. You want to use the USB enclosure attached to your "main" PC to transfer the XP install files on a HD that you will later put inside the "other" laptop, right? This line: G:\I386\winnt32.exe /syspart:F: /tempdrive:F: /makelocalsource /noreboot should work allright from 2K or XP, and unless the HD controller in the laptop is "non-standard" or SATA, you shouldn't have problems when installing. It is possible that WINNT32.EXE does not "like" the USB bus to which the target drive is attached, though. If you can try on another PC running XP it would be better and easier, otherwise you may want to try building a small PE (using the same XP source files) or use the good ol' DOS way with WINNT.EXE. You can take some ideas from the Install XP from USB Sub-Forum: http://www.msfn.org/board/index.php?showforum=157 or from this oldish thread: http://www.911cd.net/forums//index.php?showtopic=16713 AFAIK there isn't a complete "specific" guide to alternate ways to the use of /syspart /makelocalsource switches in WINNT32.EXE. jaclaz

I cannot see where it is reported the filesystem used by Zoinkity on his C:\ drive. Apart from the above and maybe other problems, the point is that BOOT.INI (or if you prefer NTLDR) does not "traverse" drives. is, as seen by NTLDR, "a suffusion of yellow" : http://www.thateden.co.uk/dirk/ Provided that the created bootsector is "correct", it MUST reside on C:\ As well the IO.SYS, MSDOS.SYS and COMMAND.COM , as well as AUTOEXEC.BAT and CONFIG.SYS MUST reside on C:\ (read on First Primary Active partition). These latter are NOT negotiable, it's the way DOS boots. (for the sake of simplicity, I am lying , COMMAND.COM can also be somewhere else if it's position is specified in config.sys) As hinted before, the use of chainloading bootsectors through BOOT.INI is the "old" way to do it, nowadays it is advised to chainload grub4dos' grldr from BOOT.INI and from it chainload directly the kernel file (IO.SYS) bypassing the bootsector alltogether, and offering a wide number of alternate methods to boot, including int his particular case, and IF the C:\ partition is NTFS, booting from a floppy image and then continue booting from D:\ ) Forum: http://www.boot-land.net/forums/index.php?showforum=66 Guide: http://www.boot-land.net/forums/index.php?showtopic=5187 http://diddy.boot-land.net/grub4dos/Grub4dos.htm Method #5: http://diddy.boot-land.net/grub4dos/files/...ll.htm#method05 jaclaz

Sure ther is a reason, point is finding which is it. Compare your setup and your settings with those in the mentiuonsed thread: http://www.boot-land.net/forums/?showtopic=4952 and krokodox's tutorials, see if you can spot any difference: http://krokodox.winbuilder.net/Documents.html jaclaz

Sorry if it didn't help. jaclaz

Well, you can still use a Repair: http://www.michaelstevenstech.com/XPrepairinstall.htm make sure source Xp install CD has been slipstreamed to the same SP level. Just for the record, we have found in another thread that a reason of this may also be entries in partition table "moved" from their "natural" order, i.e. first partition (first in LBA address) must be in first entry, second in secnd and so on. jaclaz