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

I am not at all "current" with Windows 7, it is well possible that it doesn't work as I remember, and as you describe. I would try, after having created the first partition of a given size, to hide it, disconnect and re-connect the stick, then try creating the second one. I am sure that only one partition can be accessed/mounted at a time in any Windows NT, unless the filter driver is installed, but if you each time you hide the "other" you should be able to choose which partition to access. However, I would separate the problem in two: 1) use the filter driver 2) try flipping the bit 1)I don't know if cfadisk.sys or dummydisk.sys are installable on Windows 7. If they are, it is possible that you have some "wrong" settings in cfadisk.inf (or corresponding files). You can try using this way: http://www.911cd.net/forums//index.php?showtopic=22795 which is a "generic" not "specific stick" way to have the filter working. Most probably you need to disable driver signing, but cannot say. If the filter driver approach doesn't work, you can always use manual partitioning of the stick, by using an image of it and/or a VM, but let first see if the cfadisk can work. 2)Maybe there is some misunderstanding. If you click here: http://www.mydigit.cn/mytool/ChipGenius.rar you should get a chipgenius.rar file, open it in 7-zip (or winrar) and extract from it the files: ChipGenius.exe Chips.wdb double click on chipgenius.exe, it is a GUI tool. Close it. Insert your USB stick. Re-run it. Select in the list in the upper window the USB stick that should be detected. Read in the lower window what Chipgenius knows about it. Post this latter info. I can try helping you find the appropriate "Manufacturer tool (if any available). jaclaz

IBM thinkpad's (read Lenovo) normally use a "strange" 240 heads geometry (instead of the "normal" 255 one). The flashing cursor is normally related to a mismatch/unbalancing between CHS and LBA addresses. What you can try to do is to patch the bootsector to avoid checks for CHS, a way through grub4dos is detailed here: http://www.911cd.net/forums//index.php?showtopic=23844&st=9 derived from an original idea by Clemens Fruhwirth: http://www.911cd.net/forums//index.php?showtopic=21702&st=129 http://blog.clemens.endorphin.org/2007/12/removing-chs-based-access-from-windows_3170.html which dencorso nicely compiled as a .exe: http://www.boot-land.net/forums/index.php?showtopic=8528&st=21 First thing you need to do is to check the geometry seen by grub4dos, press C and then issue: geometry (hd0) and geometry (hd1) and report feedback. Also check the data in the current partition table. These Lenovo's are making some troubles, cannot really say if we are missing something in the way they boot/behave. Compare with these: http://www.911cd.net/forums//index.php?showtopic=23408&hl= (solved) http://www.boot-land.net/forums/index.php?&showtopic=5306&st=215 (solved) http://www.boot-land.net/forums/index.php?showtopic=11320 (UNsolved) jaclaz

It is more probable that the BIOS doesn't expose the (possibly SATA) disk properly. What happens in "plain" grub4dos? Try pressing C to access command line, then issue a geometry (hd0) and a geometry (hd1) jaclaz

@bookworm The Windows NT FAT32 driver, was a commercial product by Wininternals (the read/write version), with quite a bit of limitations, including that of NOT being "bootable": http://web.archive.org/web/20020124185910/www.sysinternals.com/ntw2k/freeware/fat32.shtml but it was available a Read Only driver, with further limitations: http://articles.techrepublic.com.com/5100-10878_11-1047372.html Direct link to the freeware read only version: http://web.archive.org/web/20020124185910/http://www.sysinternals.com/ntw2k/freeware/ntfswin98.shtml The given post by fdv is pointing (point 7b) to a second driver from Ashedel (and the links is working allright): http://ashedel.chat.ru/ http://ashedel.chat.ru/fat32/ http://ashedel.chat.ru/fat32/fastfat32.rar which is said to provide bootability, but your mileage may and will vary. jaclaz

But as always some dismbiguation is needed. Do you want to INSTALL/RUN 2003 ON USB? (which is what the link fdv gave), more here: http://www.msfn.org/board/index.php?showtopic=122443 http://www.boot-land.net/forums/index.php?showtopic=9830&hl= In any case the new service to set properly the USB keys is recommended: http://www.911cd.net/forums//index.php?showtopic=22473&hl= or Do you want to run 2003's SETUP FROM USB? For which there are several methods in a dedicated Forum: http://www.msfn.org/board/index.php?showforum=157 jaclaz

Basically, you are trying to adapt an oldish solution to a newish, DIFFERENT OS, and guess what? Result is DIFFERENT. AFAICR Windows 7 had not one problem in the world in partitioning a drive marked as removable through diskpart, last time I checked. Now that you have verified empirically that applying changes to a given set of instructions may not always work, if you explain WHAT you are willing to do/create (as opposed to HOW to do/create it) I may give you some more suitable links/advice. Personally, since I hate all this mess with "Removable" vs. "Fixed", I tend to "flip the bit" in the hardware, whenever possible, and be done with it, as you may have found out in the thread you are referencing. jaclaz P.S.: Just to keep things as together as possible it seems like SPFDISK has a new home (and a much newer version - March 2009): http://spferng.myweb.hinet.net/ thanks to halohalo: http://www.msfn.org/board/index.php?showtopic=105936&st=487 Info is quite readable with google translate: http://translate.google.com/translate?u=http%3A%2F%2Fspferng.myweb.hinet.net%2F&sl=zh-CN&tl=en&hl=&ie=UTF-8

Good , that was essentially the reason why I posted it, to show you how giving partial informations is unuseful. It was intentionally "broken" to see if instead of trying to understand how it can work and write your own, you would have - as expected - simply tried to run it from a copy and paste. Try this one : @ECHO OFF SETLOCAL ENABLEDELAYEDEXPANSION SET FLAG=0 FOR /F "tokens=* delims=" %%? IN ('TYPE my_original_batch.cmd') DO ( IF "%%?"=="::BEGIN_REMOVE" SET FLAG=1 IF "%%?"=="::END_REMOVE" SET FLAG=0 IF !FLAG!==0 ECHO %%?|FIND /V "::">>my_edited_batch.cmd SET FLAG ) DEL my_original_batch.cmd REN my_edited_batch.cmd my_original_batch.cmd Hint: Check in the previous one spaces after the SET FLAG jaclaz

If I may, a small addition, there are two "BOOTCFG" programs, one in Recovery Console and one in "normal" XP with slightly different behaviour/switches. Most of the references you find around, including those on MS site are for the RC version, here is reference for BOTH: http://ss64.com/nt/bootcfg.html It seems like it's use is documented for XP only from RC : http://support.microsoft.com/kb/291980/en-us whilst on Server2003 it is detailed for both programs: http://support.microsoft.com/kb/317521/en-us These are also interesting: ( the "normal" bootcfg is in XP PRO but not in Home) http://support.microsoft.com/default.aspx?scid=kb;en-us;289022 http://support.microsoft.com/kb/303980/en-us jaclaz

And again, you should explain the problem you are having (as opposed to the way you think it should be solved). There is no problem in removing lines, as long as they are "unique" in the batch, but since you probably have several lines like "ECHO." you cannot use "ECHO." as a simple argument for FIND or FINDSTR. Also parsing the batch can be simple or difficult depending on it's contents. An example is this one: Running something like this: SET FLAG=0 FOR /F "tokens=* delims=" %%? IN ('TYPE my_original_batch.cmd') DO ( IF "%%?"=="::BEGIN_REMOVE" SET FLAG=1 IF "%%?"=="::END_REMOVE" SET FLAG=0 IF !FLAG!==0 ECHO %%?>>my_edited_batch.cmd ) DEL my_original_batch.cmd REN my_edited_batch.cmd my_original_batch.cmd Will remove anything between the two "tags", but it simply won't work if you have redirection or piping symbols in your original batch. jaclaz

Nice find! Here is an explicit link to the "other thread", where all the info is, just in case friendly names will be botched again at next board update: http://www.msfn.org/board/index.php?showtopic=143980 jaclaz

Maybe a suitable temporary solution: http://www.intelliadmin.com/index.php/2006/07/disable-floppy-drives/ jaclaz

As a side note, and only as a "philosophical" point, with no practical use whatever , the only "bad" thing that can happen if you try mkdir giving an existing directory is that an error message will be output to STDERR, I have no idea (but it may be worth a test ) if by unconditionally making the dir anyway would it be faster than looping to the "directory" IF NOT EXIST, when a great number of file needs to be copied. I.E. something like: FOR %%? IN ( "%ProgramFiles%\Winamp\Plugins\gen_MSN.dll" "%ProgramFiles%\AIMP2\Plugins\gen_msn7.dll" ) DO CALL :Copyfiles %%? GOTO :EOF :Copyfiles MD "%~dp1" >NUL 2>&1 IF NOT EXIST "%~dpnx1" COPY "%~nx1" "%~dpnx1" GOTO :EOF jaclaz

Yes , as said, if your drive motor does not spin up when it is connected to power (even with NO data cable connected) and beeps, it is ANOTHER problem from that discussed on this thread, so please start ANOTHER new thread, where maybe it will be possible to help you without further cloggering this thread. In a nutshell, when a drive of this kind is powered it should: start spinning try to read calibration data NOT beep even if it's "bricked" with BSY and LBA0 problems... This is not the behaviour you described, hence this is not the right place to talk about this problem. Read here: http://forums.seagate.com/t5/ATA-and-Serial-ATA-drives/Seagate-7200-11-Drive-Beeping/m-p/39439 then start a new thread about your issue. If this started happening since when you have removed the PCB ONLY, (and it didn't beep and it did spinup before) it means that somehow contacts are not as they should be. In other words, carefully and thoroughfully clean contacts, completely re-assemble the drive an PCB, and make sure that the drive operates "normally" (meaning NOT beeping AND spinning up) then check if it has a BSY or LBA0 problem. Until you are in such a condition, this is simply not the appropriate thread to try and help you. jaclaz

Please read, slowly, point #1 here: Pseudo-code: IF NOT LBA0 THEN IF NOT BSY THEN GOTO :Start_New_thread Your drive has probably the motor or motor controller stuck, nothing connected with the problems this fix can solve. @Phenom9 No, we cannot be 100% sure of anything, this is somehow a "hack", it is very possible that a little something has changed, but same applies to you, start a new thread if you need help in recovering those spanned volumes. jaclaz

Find the installation directory where files were copied by the original install. If the file HSBR-MP.EXE or the README weren't deleted, it is likely that they are part of the problem. Windows search for "HSBR" should be enough. Once you find these files, try searching the registry for their name. Also, there quite a lot of "registry fixing" programs that can remove an app from the list of installed apps, Regseeker comes to mind: http://www.hoverdesk.net/freeware.htm jaclaz

Yep, I mean which size is it detected with? If 0 you have a LBA0 problem: Clicking sound may be connected with a problem with the hard disk (lost calibration data) which is NOT resolvable without some specific software/hardware and knowledge. jaclaz