jaclaz

Yep. On another board, in another time, I was the Finder . @Kmuland If you weren't able to follow my explicit link to fdv's page on the linked to thread, you might have missed the one by Ambassador that pointed to: http://www.msfn.org/board/index.php?showtopic=135865 where BogdanV made some more progresses. However, if I may, it's the goal that you have that is: very difficult mostly pointless There are a number of fully working alternate shells and fast file-managers that work allroght in XP/2003 if you want it more responsive/faster. I mean, with all the hacking and tweaking in the world, it is UNprobable you will get a reliable 2K shell under 2K3, if it's fo r fun and to experiment a bit, it's allright, but definitely not for a "production" system. jaclaz

JFYI, you should search on "dedicated" sites. Hint: http://www.robvanderwoude.com http://www.robvanderwoude.com/search.php You may be able to find : http://www.robvanderwoude.com/clevertricks.php http://www.robvanderwoude.com/clevertricks.php#PUSHD_UNC jaclaz

The problem with batch is that the file contains redirection symbols <> and % signs, and also quotes ": this may prove to be a very hard problem to get around. Mind you, it may be possible to do it in pure batch, but definetly NOT worth the effort. To get an idea of the complexity involved, check this: http://www.robvanderwoude.com/xtreme.php http://www.robvanderwoude.com/files/cvturlnt_nt.txt The use of an external program is far better/easier/foolproof, besides sed, I am personally fond of gsar: http://home.online.no/~tjaberg/ jaclaz

There are almost NO reasons (on a single user PC) to use NTFS if not the volume size that is limited in FAT16 to 2 GB (Ok, 4 Gb, but DO NOT use 4Gb FAT16 volumes!). Sure NTFS is faster on BIG volumes, and has better recoverability, but you don't actually *need* it's features. You have to understand that NT 4.00 was a "TOP" OS when "normal" hard disks size were around 500 Mb÷1 Gb, and a 2.1 Gb one was considered a *huge* disk, let alone a 4.3 Gb one. I have been working (and I mean working, not "playing") on systems with a 2.1 Gb HD, partitioned in such a way that I could backup with three CD's (plus some little "spare" space). A "standard" NT4.00 install is around 150 Mb, if I recall correctly, I had an "emergency" NT (simply with a number or unused system files and all help files removed) around 50 Mb on a ZIP disk (which also contained some importeant data). The "right" size for a NT4.0 partition is below 1 Gb. (assuming that you have a separate partition for the DATA). As areference, a typical setup I used in years like 98/99 (before 2K came out) was: C: Primary Active partition, FAT16, 1Gb <-DOS 6.22 + Emergency NT (a copy of the 50 Mbish described before) EXTENDED PARTITION containing: D: Logical Volume Windows 95/98, FAT32, 1 Gb (yes, it is possible to install Win9x on a Logical Volume) E: Logical Volume NT 4.00, NTFS, 2 Gb F: Logical Volume 9xDATA, FAT32, 2 Gb G: Logical Volume NTDATA, NTFS, 2 Gb H: Logical Voume DATA, FAT16, 1 Gb I: Logical Voume DATA, FAT16, 1 Gb L: Logical Voume DATA, FAT16, 1 Gb And yes, the disk was around 10 Gb, and I had 2 Gb sized backup solution. jaclaz

Well, what you report seems more like I remembered it. If I were you, I would leave everything "as is", and wait to do further tests when you happen to get another stick that doesn't work as you want it to. About the "hard way", the link I posted is a direct link to page where actual "Manufacturer Tool" that are (or better should be) appropriate for your stick. You download one, and you try running it (WITHOUT the stick connected). You try and see if there is an option (they do have an english interface) that *resembles* what you want to do. IF there is (not *ALL* controllers or not *ALL* utilities have this feature) you try it. Now you do understand why the , don't you? Some utilities are "easy", some are "difficult", it is more a gambling game than anything else. So, DO NOT do it. If you are curious, just download them and try running them with NO devices attached, to see how they "feel". You are now a happy bunny in the basket , don't make things that may make you become a depressed one . http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Check how fdv tested the NT4 shell (which is even faster) on 2K, possibly a method that is similar may work. http://www.msfn.org/board/index.php?showtopic=138242 jaclaz

Another happy bunny in the basket. http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Yes, please (this way we have a final confirmation for cfadisk.sys also). Yep, that's the "old" way (and prone to errors/inconveniences, as you "attach" the filter to a specific hardware device). The new "generic" way by cdob simplified and examplified in the referred to thread by online: http://www.911cd.net/forums//index.php?showtopic=22795 should be (please read as "is") more tolerant, as you "attach" the filter driver to the whole "USBSTOR\GenDisk" it should/will work for ANY USB stick, see the original post: http://www.msfn.org/board/index.php?showtopic=126868&st=12 No, sorry for the misunderstanding, the Vid and Pid you had already posted was enough to find the (supposedly) "right" tool for it. That was referred to eventually risk using on your stick the linked to Manufacturer's Tool to "flip the bit" of the controller. As said, this - if possible with that tool - is the most "definitive" way, but it implies some risks of "botching" the stick for good. Thus I can "recommend" it as the "right" thing to do (in the sense that you won't have anymore ANY problem with Fixed vs. Removable under ANY OS/install, without needing EVER to reinstall the filter driver), but cannot actually "recommend" doing it , as it involves the said risk, and don't want to be "held responsible" for accidentally ruining someone else's stick permanently. I personally "flip the bit" of all my sticks, but never used that particular Manufacturer Tool, so, I cannot even say if it allows doing it, let alone know if it's "friendly", "easy" or not, it's all up to you. More generally, my personal approach is somewhere between : and: it's your choice, you only know if you have the experience, knowledge, and ultimately "guts" to risk doing a firmware change, after having judged if you need it at all or if you are happy with the filter driver. jaclaz

I may add that should anyone want to know what problems (and "features") the "HP Format Tool" has, and the problems about CHS and LBA balancing, the info is available (besides the problems with bootsectors code of NTFS and FAT32 invoking NTLDR, already discussed), read here: http://www.boot-land.net/forums/index.php?showtopic=2246&st=15 http://www.911cd.net/forums//index.php?showtopic=21702&hl= http://www.911cd.net/forums//index.php?showtopic=21049&st=14 To this you add that some motherboards apparently need a fake second partition: http://www.boot-land.net/forums/index.php?showtopic=7512&hl= And you will have an idea of how "crazy" is this whole "USB booting" staff. jaclaz

Excellent. Another nice way to introduce a possibly risky variation for NO apparent reason whatsoever. Out of curiosity, WHICH cardstock will you pull out FIRST? Or are you planning to build a robotic arm to pull BOTH at the same time? jaclaz

Look, I have spent a reasonable amount of time to try and write a (hopefully) easy to follow READ-ME-FIRST, EXACTLY to AVOID having to reply yet another time to SAME questions. http://www.msfn.org/board/index.php?showtopic=143880 WHAT is the difficult part in it? However, let's see if I can put it in a quick Q&A form: Q1: Will it work if I DO NOT connect the GROUND? A1: Who knows? Maybe yes, maybe not, there are so many factors involved, including if using a RS-232 or USB converter, a battery or the PC PSU to power the converter, a laptop or a desktop and the actual Power supply used to power the HD, that there is NO way to know in advance. We have so many posts of people whining about being unable to connect or seeing only gartbage on the screen WITHOUT proper GROUNDING that we have lost count of 'em, so I would say that on average NO, it won't work. Q2: Will it work if I connect properly ALL involved equipment to GROUND? A2: YES. Make your choice... ...but choose wisely... http://www.imdb.com/title/tt0097576/quotes I'll try again: Does Carter appear to have been using the known exception? Or a Pololu converter that can be powered by ANYTHING in the 3V up to 5.5V range? http://www.mapleleafmountain.com/seagatebrick.html http://www.pololu.com/catalog/product/126 Evidently giving on the TX line ANYWAY the "right" TTL level if powered at +5V? jaclaz

I take this for a final confirmation that Anton Bassov's dummydisk.sys with the approach that online so nicely detailed: http://www.911cd.net/forums//index.php?showtopic=22795 works allright under Windows 7. (Did I get it right? You don't mention which driver you finally installed. ) However, if dummydisk.sys works, also cfadisk.sys should work with the generic method by cdob, if you hava an occasion to try again it, please report. Yes, most probably you did not manage to intall them correctly or fully. Writing .INF files is tricky business, you have probably missed some bit. Well, that's enough: it seems like a kingston using a SSS chip: http://www.flashboot.ru/index.php?name=Files&op=cat&id=17 http://translate.google.it/translate?u=http%3A%2F%2Fwww.flashboot.ru%2Findex.php%3Fname%3DFiles%26op%3Dcat%26id%3D17&sl=ru&tl=en&hl=&ie=UTF-8 most probably a SSS6690 (just in case yu want to take the HARD way) You are welcome. jaclaz

YEP , but one that owns a partition magic or acronis disk director license doesn't apply anymore for "poorman" This may help : http://www.users.globalnet.co.uk/~jeacocke/fat16to.htm http://support.microsoft.com/kb/273896/en-us http://www.mdgx.com/secrets.htm#FDPT http://www.unusualresearch.com/cvtfat32/cvtfat32.htm ftp://ftp.sac.sk/pub/sac/utildisk/cvt16-32.zip but you may need to rewrite the bootsector invoking NTLDR In this specific case, since at a given time the working OS has to be copied to the "target" partition, that if I get it right is not to be touched/re-formatted, the poorman's way has to be used anyway. jaclaz

The converter doesn't "out" ANYTHING on the Vcc (Vcc is the power input of the converter) It's signal levels (TX) are in the LOWER TTL range if powered at around 3V, which is the one documented to work. (again read READ-ME-FIRST), point # 11) in this case. Read this also: http://www.msfn.org/board/index.php?showtopic=128807&st=2330 http://www.msfn.org/board/index.php?showtopic=128807&st=2332 jaclaz

That's exactly the problem. Basically you are trying to do something that is: UNdocumented UNintended by the people that wrote the OS and install routine UNintended by the good guy that wrote the FAT32 driver and that has NEVER been reported as doable (AFAIK) Sure, you can try, it may work or fail to, we don't know. BUT the actual setup is done by SETUPLDR.BIN, I won't offend your intelligence giving info about this file. No, that is one out of the several hard parts. Mind you, I am not trying to put you down, simply you are a self-declared non-expert tryng to do something very, very complex, and at first sight missing the very basics: learnign to wak before start running. On the other hand : Since you came here to get help/advice, you should be ready to get some: The *IMPOSSIBLE* way: ATTEMPT to install DIRECTLY to a FAT32 partition Find, all together, ANY number of problems Isolate one of them, find a solution for it and loop to #1) until you solved ALL of them The *DIFFICULT* way: FORGET (temporarily) to install DIRECTLY to a FAT32 partition Install to a FAT16 one Re-install with the integrated drivers on FAT16 Re-install with the integrated drivers AND with the exchanged NTLDR and SETUPLDR.BIN (which will probably "carry with them" NTDETECT.COM) on FAT16 IF everything works as expected, try installing on the FAT32 The *EASY* way: FORGET (temporarily) to install DIRECTLY to a FAT32 partition Install to a FAT16 one Add the drivers, test they work to access another FAT32 partition Add the exchanged NTLDR(which will probably "carry with it" NTDETECT.COM) on FAT16 DO a poorman's backup Re-format the FAT16 partition as FAT32 DO a poorman's restore IF everything works re-do steps 5) and 7) restoring to the "final" FAT32 partition A poorman's backup is hinted about here: http://www.msfn.org/board/index.php?showtopic=118623&st=48 The good thing about NT4 is that it's not picky at all about drive letters and System volumes (unlike 2K and XP) but still you need some knowledge on how to manage the drive/partition moves. jaclaz

It seems to me quite clear, if you re-read what you quoted: The original info's were about completely detaching the PCB (thus insulating BOTH contacts). Re-assembling the PCB whilst powered on is tricky and risky, as it is possible that the motors don't get enough current (for the lack of ground connection) and some components on the board will overheat. Using a cardstock (and quickly and fully tighten the screws) is much easier and avoids possible mis-placement of the board or wrong contacts (that may blow the PCB). So, you have to choose WHICH contacs to put the cardboard between. And the answer, is, as it seems to me clearly written in the quote: try with the HEADs contacts. If it doesn't work on your drive, try with the MOTOR ones. We don't have a database of which contacts for which model are better, but you do not risk anything by using trial and error, in most cases #1 will work, in some it won't and you'll have to use method #2. jaclaz

Your real problem is NOT reading the READ-ME-FIRST (and try understanding what is written in there): http://www.msfn.org/board/index.php?showtopic=143880 Since you have a DIFFERENT problem from the ones this thread is related to, start a NEW, SEPARATE thread DESCRIBING fully your problems. Till now you have posted two times (in the WRONG place) without giving ANY useful info. Start a NEW thread. Describe FULLY what happened and how and when it happened. Use this as a quick reference: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html jaclaz

The photo is to get an idea, the fact that the drive needs to be normally powered is implied. Why don't you FIRST read the READ-ME-FIRST ? : http://www.msfn.org/board/index.php?showtopic=143880 Where you can find that the RECOMMENDED guide is another one: As it has clearer photos and more explicit text? http://www.mapleleafmountain.com/seagatebrick.html jaclaz

And nobody mentioned fsutil...! : http://www.msfn.org/board/index.php?showtopic=143446 @ECHO OFF FOR /F "tokens=1,2 delims=\" %%A IN ('MOUNTVOL^|FINDSTR [C-Z]:\\') DO ( FOR /F "tokens=1,* delims=-" %%B IN ('fsutil fsinfo drivetype %%A^|FIND /I "CD-ROM"') do ( ECHO Checking drive %%B ... IF EXIST "%%B\OEM\RunOnce\Auto Setup.bat" CALL "%%B\OEM\RunOnce\Auto Setup.bat"&GOTO :EOF ) ) ECHO \OEM\RunOnce\Auto Setup.bat NOT FOUND PAUSE jaclaz

What do you mean? The name is PIA->Programa de Instalacion Automatizado (in English it would sound like AIP Automatic installation Program) http://pia.windowstitan.com/index.html Translates more or less to: jaclaz

Not really. (which in this particular case means yes ). Basically NTLDR is a "mini-OS" or "embedded-DOS". When you boot this part of the executable loads a "real mode OS" that is used to load the NT kernel and drivers i.e. the "protected mode". The NT4.00 NTLDR obviously knows nothing about FAT32 so it cannot simply access the volume is on if formatted FAT32. In other words, when you want to boot from a filesystem that is not supported under NT, you need to have BOTH a compatible NTLDR and the filesystem driver for the "protected mode". The 2k (and later) NTLDR instead do support FAT32, so you can try also the one from XP or 2003. Hard to say between the 2K, XP or 2003 which one loads "better" NT 4.00, surely the 2K one is "near in time" to the NT 4.00, so it would be my first choice for such a test. To actually install NT on a FAT32 drive, as fdv pointed out, is not possible without integrating these drivers in the NT4 source and it's not easy as it may seem. (at least I have never seen this kind of integration detailed). Sure, but you are asking a question which solution requires being an expert, so you may possibly be in a CATCH 22 . jaclaz

With all due respect , why everytime someone is having some fun with good ol' BATCH, someone else comes around saying that VBS or POWERSHELL would be better? I was actually expecting gunsmokingman to post one of his nice .vbs's .... jaclaz

@Yzöwl I am not sure to get it. The CDROM variable is set to C:\ on first run, unless you add a SET CDROM= after the IF EXIST: @ECHO OFF SETLOCAL (SET CDROM=) (SET MYBAT=OEM\RunOnce\Auto Setup.bat) FOR /F %%# IN ('MOUNTVOL^|FINDSTR [C-Z]:\\') DO CALL :SUB %%# IF NOT DEFINED CDROM ECHO=Correct CD-ROM Drive not found! GOTO :EOF :SUB IF DEFINED CDROM GOTO :EOF (SET CDROM=%1) IF EXIST "%CDROM%%MYBAT%" CALL "%CDROM%%MYBAT%" (SET CDROM=) the CDROM is always defined as C:\ and the IF EXIST is never executed for any other drive but C:, if it is, then you have the same problem I was talking about the accessing of devices with letters but no actual media. jaclaz

I must have misunderstood the problem. I thought you were meaning that the install (once copied to HD) didn't boot. If I am understanding right now, it's the USB stick that doesn't boot at all. If so, this is another problem, about stick bootability, as cdob pointed out. I guess your best bet is to re-partition/re-format the USB stick with RMPREPUSB and just verify it's bootability on those machines: http://www.boot-land.net/forums/index.php?showtopic=7739 or, if it doesn't work, try the other utilities listed here: http://www.boot-land.net/forums/index.php?showtopic=9460 What you want/need is a stick with: NTLDR BOOT.INI (with at least two entries in it) that can boot up to the BOOT.INI choices. FAQ #10 in my old page: http://jaclaz.altervista.org/Projects/USB/USBfaqs.html still provides a reasonable troubleshooting path. The news are (see my previous post) that if for any reason CHS and LBA are not "balanced" the stick may boot with FAT16 (06 or 0E) and may not with FAT32 or NTFS due to the additional check in the bootsector. The DOS/Win9x bootsector (for FAT32) appears like more tolerant, but it's all about how different BIOS behave. jaclaz

The "usual way" is something like: FOR %%A IN ( Z Y X W V U T S R Q P O N M L K J I H G F E D ) DO ( IF EXIST "%%A:\OEM\RunOnce\Auto Setup.bat" set CDROM=%%A:&GOTO :Out_of_loop ) ECHO Echo No CDROM unit found PAUSE GOTO :EOF :Out_of_loop ECHO HERE are the other commands Problem is that in some PC's a Sd card slot or a stoopid multi-card readers provide a drive letter even if no media is present and this will cause a popup window when you try to access the device. Something like this should work, however: For /F "tokens=3,5 delims=\ " %%A IN ('REG QUERY HKLM\SYSTEM\MountedDevices /s ^|FIND "\DosDevices\" ^| FIND "4300640052006F006D"') DO IF EXIST "%%A\OEM\RunOnce\Auto Setup.bat" set CDROM=%%A:&GOTO :Out_of_loop ECHO Echo No CDROM unit found PAUSE GOTO :EOF :Out_of_loop "4300640052006F006D" is the binary for "CdRom" which should be present in any dosdevice that represent a CD or DVD drive. jaclaz