jaclaz

Yes it should mean that, strangely enough, the modified .iso works allright. (that was the feared issue, more often than you would like .iso's modified with .iso editors don't boot properly anymore/have strange quirks , expecially XP setup related ones, errors like missing txtsetup.sif, etc. are common) jaclaz

#1 is expected behaviour. #2 is strange, the "beautify.cmd" is the one that should revert the "§#§" and "§##§" to their original values. ::Restore changes made to make the .inf "batch compatible" ::Replace dummy string "§#§" with "==" CALL :run_gsar :xa7:x23:xa7 :x3d:x3d ::Replace dummy string "§##§" with stoopid "&" CALL :run_gsar :xa7:x23:x23:xa7 :x26 Are you sure you did run the beatify.cmd on the file? Anyway I will try to reproduce and fix. #3 should mean that somehow something was a-miss (a variable got a value of "space" or "tab") I will try to reproduce and fix , the other quirks should be easily fixable #4 yes, this was expected in case of duplicated sections, I'll put a check for such duplicated entries so that these sections will be merged when split (I do know that is sounds queer, but it is how it will work ) jaclaz

For the record it is very possible, just use El-Torito "Hard disk emulation" (instead of "Floppy emulation" or "No emulation"). Or you mean a super-floppy format? Maybe one can use the Hard disk emulation with a "dual-mode" MBR/Bootsector like the makebootFAT one. @rloew Which media type do you need for a super-floppy larger than the 2.88 Mb? Standard ones are: 0x00 - No Emulation 0x01 - 1.2 Mb floppy 0x02 - 1.44 diskette 0x03 - 2.88 diskette 0x04 - Hard disk emulation @Multibooter, sorry for the OT. If you are interested in the matter can you start a new topic "CD related"? @rloew, maybe we can continue this interesting discussion on the above new thread? jaclaz

Well, you posted about XP, Vista and 7, not about three versions of XP. Yes, you should change the NTDETECT.COM in the three \I386\ but you need to ALSO change it into the .iso, READ the given thread. jaclaz

Are you sure you have an \I386\ for Vista and 7? With a NTDETECT.COM in them? And yes, normally you change it in the \I386\ of the XP (and or 2003) source, before running WinsetupFromUSBwithGUI or you will need to change it also inside the actual .iso, see here: jaclaz

Maybe useful, maybe not. http://reboot.pro/12436/ jaclaz

NOT the intended "final" result, ONLY "intermediate steps". Find attached three batches. splitinf.cmd - to split an existing .inf (run it with one parameter, the original .inf) join_inf.cmd - to join the split parts created by the above (run it with one parameter, the SPLIT_ directory) beautify.cmd - to make the result more readable and reset some changes I have to do to the Split parts to process them easily in batch gsar is needed: http://home.online.no/~tjaberg/ Basically: create a directory (please NO spaces in paths or filenames) like C:\INFTEST put in it the batches, gsar.exe and the (basis)Windows2000-KB891861-v2-x86-ENU.EXE.inf (please rename it to something manageable, like "base2K.inf"), never use in filenames characters that are parsed by the command line, like "(", ")", "&" "|" and interpreted like commands or are however part of syntax or need to be escaped normally, even if allowed on the filesystem, see here: http://en.wikipedia.org/wiki/Filename (please note how right now the batches do use "[" and "]" so may be not good on a FAT filesystem, please use them on a NTFS one) open a command prompt and navigate to the directory you made: CD /D C:\INFTEST run: splitinf.cmd base2K.inf join_inf.cmd SPLIT_base2K beautify.cmd JOINED_base2K.inf the "end result", i.e. BEAUTY_JOINED_base2K.inf should be comparable with the original base2K.inf and be a "fully" working .inf file If not, post which problems there are. Once we get these steps working successfully, we will talk about the actual merging of the "base" with another "split" file.... Also, I have noticed that in some of the "example files" there are many "empty" sections, are they actually *needed* (right now they are mantained as they are)? Please note how the above are early, preliminary tests and the actual .cmd's need to be cleaned and polished a lot (and quite a bit of "error controls" need to be added to them). jaclaz split_inf.zip

Molecule I am getting maybe half of what you probably mean, I never saw such a behaviour. Unless you - instead of talking of "foreign powers" and "locked open backdoors" - post something meaningful (like the EXACT steps you made to install the 2K, WHICH programs you post-installed to it, etc. etc.) it would be difficult or impossible to help you troubleshoot the issue. 512 megabytes is enough to run a "normal" 2K with no pagefile.sys, for experimenting, I use normally a laptop with 128 Mbytes of RAM and a 256 Mb of pagefile, fixed size, of course without running on it programs requiring lots of RAM and with a reduced number of running services. I do understand how you are annoyed by the whatever is happening on your system, but ranting about MS, suggesting yourself what is the cause and telling us what you want to hear and what you don't want to hear about possible ways to solve the problem may make things unneededly more complex. jaclaz

Why? I mean there is no need of Partition Magic. You can use the filter driver and make the stick "fixed", then partition it "normally" or, unless I am mistaken, since Vista diskpart can be used "directly" on a stick. jaclaz

Sure, you will need a multimeter and some very basic knowledge on how to use it. See here: But once you have found out it actually is a TVS shot, what are you going to do? There may be REASONS why the TVS diode is short-circuited, and removing it may "fry" something (the whatever the TVS diode "sacrificed it's life" in order to protect). It is also possible that it was just a transient on the power line, but if you don't know how to check for a shot diode, with all due respect , I doubt you are able to diagnose the actual cause. jaclaz

Yes/No. The cause may be the particular version of the grub4dos MBR (for the Acer's) or a problem with partitioning/formatting (more likely for the HP's). Typically you should: use beta 7 (latest) use RMPREPUSB to initialize/partition/format the stick (use 2PTNS settings) in case get latest RMPREPUSB try on the "pesky" machines report what happens As an alternative, you can backup your existing stick (with something like the NT backup, i.e. "file-based"), repartition/re-format it with beta 7 (or directly with RMPREPUSB - advised) then restore the files from the backup. In BOTH cases YMMV, if you want to actually troubleshoot the issue, start a new thread an post some EXACT details of HOW the stick is setup/partitioned/formatted AND the exact models you have problems with. Same goes for the Dell's, provided that you already read attentively the FAQ's and complied with what is in them (modified NTDETECT.COM, SATA integrated). jaclaz

If the PSU shuts itself off you have a shorted TVS diode. If BOTH TVS diodes are OK, you will need to try an external USB enclosure. DO NOT try the disk drive into an external enclosure until you are POSITIVE the TVS diodes are OK, as most external power supplies have NO protection against short circuits and will simply burn. Do not underestimate the amount of power (Amps) the drive may drain at spin-up, expecially if it has a "sticky" bearing. In other words, it is possible that your current PSU does not provide enough power, and first suggesdted course of action is to try the drive in another PC (surely working) and with only that drive connected to the PSU (in the sense of no other disk drives connected). jaclaz

@nilkanth It seems to me like your post is completely void of any relevance to the actual topic. As soon as you will acknowledge this post, I will split posts related to your issue to a new topic, where it will be easier to help you without "polluting" the present one, that is intended as an "experimental" one, nothing that you should (for the moment) try at home, as ilko_t pointed out there are several tested and working methods, it is pointless to use a harder way to get the job done, unless it is for "fun" or for the sake of experimenting. jaclaz

Check, double check, triple check, contacts, cleaning them thoroguhfully. See here: Try tightening a little bit more screws around contacts after having removed the cardboard. jaclaz

Something like: @ECHO OFF SETLOCAL ENABLEEXTENSIONS SETLOCAL ENABLEDELAYEDEXPANSION SET /A Counter=0 FOR %%A IN ( "c:\windows\prefetch\*.*" "c:\windows\temp\*.*" "%homepath%\Appdata\Local\Temp\*.*" "c:\temp\*.*" "%homepath%\Local Settings\Temporary Internet Files\*.*" "%homepath%\Local Settings\Temp\*.* ) DO ( CALL :do_count %%A CALL :do_del %%A ) GOTO :EOF :do_count FOR /F %%B IN ('dir /b %1') DO ( SET /A Counter+=1 ECHO !Counter! ) GOTO :EOF :do_del ECHO del %1 GOTO :EOF jaclaz

Sure . It takes only a few lines of batch to implement the file version check, and as well only a few lines of code in C or in C# "standalone", if using .Net, it will take a few lines + a considerable amount of ".Net", with all the consequent .Net install and versioning problems on 2K. At it's basics: @ECHO OFF :: V_copy.cmd - small batch sketch :: to copy executables and dll's depending on their version SETLOCAL ENABLEEXTENSIONS SETLOCAL ENABLEDELAYEDEXPANSION SET SOURCE=%~dpnx1 IF "%2"=="" GOTO :ERROR2 SET TARGET=%~dpnx2 SET TARGETDIR=%~dp2 IF "%TARGET:~-1,1%"=="\" SET TARGET=%~dp2%~nx1 IF "%~x1"=="" GOTO :ERROR1 IF NOT EXIST %SOURCE% GOTO :ERROR1 IF NOT EXIST %TARGETDIR%\NUL CALL :ERROR2 FOR /F "tokens=1 delims=[]" %%A IN ('fvertest.exe %source%') DO ( SET V_source=%%A ECHO %source% version is %%A FOR /F "tokens=1 delims=[]" %%B IN ('fvertest.exe %target%') DO ( SET V_target=%%A ECHO %target% version is %%B fvertest.exe -v %%B %target% REM Insert here checks based on Errorlevel and "UNecho/modify" the following ECHO Errolevel is !ERRORLEVEL! ECHO COPY /B %SOURCE% %TARGET% ) ) SET V_ GOTO :EOF :ERROR1 ECHO. ECHO SOURCE %source% is missing GOTO :EOF :ERROR2 ECHO. ECHO TARGET %target% is missing GOTO :EOF Please note how the above is V_copy.cmd and NOT V_xcopy.cmd. jaclaz

I would use fvertest and avoid .Net Here: http://www.westmesatech.com/wast.html @dencorso I am failing to see the practical implications. Do you mean that there are executables around with SAME "hex" version BUT different "text" version and that the latter may be newer than the first AND that it is a reliable way to get the newer file? jaclaz

I just gave you some friendly advice as you are a new member and it was possible that you overlooked that part . Obviously you are perfectly free to follow your own understanding of the mentioned bit. As well, have you read the part on the top of this thread that reads?: jaclaz

Have you checked ATTENTIVELY the Rules, particularly #1.a ? http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules jaclaz

Did some tests, and the matter is a bit complex, but now I can say it can be done, though not with "ini related" tools, since the .inf seem like having a "queer" set of rules. Don't expect anything too soon, but I have great expectations from a new approach I just took ... jaclaz

Check also here: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules point #11 . jaclaz

Be aware of going too far down the memory lane.... http://www.911cd.net/forums//index.php?showtopic=21702&st=122 it shows your age... ...Why, in MY day.... http://reboot.pro/1908/ jaclaz

You are right these particular .inf files need some "special treatment". There are lots of "beautifying" uneeded spaces that create havoc! Additionally you simply cannt write properly with FEDIT something that is ALREADY between double quotes (like "$Windows NT$"). I'll do some tests with batch and a bunch of utilities and let you know. jaclaz

From the article : jaclaz

Have you actually tried FEDIT? Can you post a single example of a "base" update.inf + a couple examples of the files to be merged? jaclaz