jaclaz

Why not using any of the available programs? http://www.programmersheaven.com/download/14090/download.aspx http://www.kime.net/directcc/directcc31.htm jaclaz

Good news , though it's strange, or maybe it is some "by design" feature from MS, something like "if a file called test.txt - or any file with extension .txt - is found in $OEM$\$1 it is deleted during install". You know, something like having a .txt file beginning with ".LOG": http://support.microsoft.com/kb/260563/en-us only not reknown as that one Only too happy to know there is now another happy bunny in the basket. http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Maybe because he/she doesn't understand English? (exception made for a few English foul words, of course )? jaclaz

Yep , but as you know nlite has NOTHING to do with the "installed" system. What you need to use is Offline Sysprep: http://www.911cd.net/forums//index.php?showforum=43 either the "whole thing" (STRONGLY recommended) or just either the Driver Injection GUI: http://www.911cd.net/forums//index.php?showtopic=22523 or the MSSTMake: http://www.911cd.net/forums//index.php?showtopic=22313 jaclaz

There may be , but definitely it is something that happens NOT in the "grub4dos" part. grub4dos has NO provisions to write to the filesystem (meaning the filesystem structure), so it cannot delete (or create if that matters) files. grub4dos has however direct access to disk sectors, so what you can do is write with grub4dos dd a "status byte" to the MBR and later remove it from the booted installed windows with an utility like MBRFIX (called by RunOnceEx or similar) which happens to have exactly this feature. You can then use the checkrange function to read the byte and use it as "conditional" switch. Check this thread: http://www.boot-land.net/forums/index.php?showtopic=12449&hl= for an example use of checkrange that will also probably be used in next version of WinSetupFromUSBwithGUI. Or you can dd a whole sector file to an unused sector, say sector 62, and then wipe it with an utility like dsfo/dsfi. Check this thread for a (complex and seemingly unrelated) example: http://www.boot-land.net/forums/index.php?showtopic=7138&hl= grub4dos has also the write command that can write to an already existing file, but it's use seems to me like not suitable for your needs. Or you can use another way, you can check which files are on the HD after the first part of the windows setup and that are NOT there after second part (because they are deleted by the normal second part of the WinXP install, and check for one of them (this way you won't need the $OEM$\$1). Out of my head (and without actually checking), I would try checking for the presence of "migrate.inf" . Finally, you can use one sector of the USB thingy or even the actual "F6" firadisk floppy to store this "flag", this way you won't even touch the target HD (though this won't help much in the case of a "stoopid" user that could break the "normal" sequence" - which is the actual only thing that you can "flag" this way). If this is OK, you can also re-write while booting the .lst file using the mentioned write command. A simpler way (still at the risk of the "stoopid" user breaking a sequence would be to use the hiddenflag command making use of the second "dummy" partition RMPREPUSB creates, find here some reference: http://www.boot-land.net/forums/index.php?showtopic=12437&hl= together with some more examples of the "live dangerously with grub4dos" series : Also, this is grub4dos and NOT "grub" (which doesn't exist, there is GRUB (legacy) and GRUB (2) and grub4dos), though they have several things in common and even a few developers have contributed to two or all three of them, they are DIFFERENT projects and syntax, EXPECIALLY the "advanced" one is different, sometimes slightly, sometimes greatly. jaclaz

Maybe this helps: http://www.robvanderwoude.com/2kprintcontrol.php (or maybe not ) jaclaz

To be picky, "in order to be able to format partitions larger than 32 Gb to FAT-32 under XP". For the record, there is also Tokiwa FAT32 formatter (GUI): http://tokiwa.qee.jp/EN/Fat32Formatter/ and SwissKnife: http://www.compuapps.com/index.php?option=com_content&view=article&id=112:swiss-knife-v322&catid=48:drive-managment&Itemid=193 that works allright under Win9x/Me. jaclaz

Well, then I really don't get it. Are you saying that you actually read the suggestions, ignored them, and then, in order to have the stoopid link working you had to actually follow them? Point #7 was written BECAUSE of the problems inexperienced people had WITHOUT grounding and says in a nutshell "ALWAYS ground EVERYTHING together". Since Snakebyte2 thought the original wording (which is the one on page 154): was not clear enough I asked him to provide some suggestions to make it more clear (current text on the READ-ME-FIRST). As well you are welcome to PM me suggesting any possible bettering to the scope of making that part more clear. jaclaz

Good . Believe me, NOT to make any fuss about this , but since the dawn of time (NT 4, Win9x, etc.) the standard troubleshooting of a non-bootable Windows has been : boot the system with "something" else, like a second install, a boot CD, etc. verify the integrity of the filesystem (through CHKDSK or other similar utilities) and if needed fix it then, if the above is not enough: make a new backup of the (offline) Registry and - if available - replace it with a backup copy of it then, if the above is not enough: since Windows 2K, make a repair install then, if the above is not enough and everything else has been attempted and failed, like: removing ALL hardware leaving only HD, Video card, monitor and keyboard connected safe mode command line mode etc. eventually give up and do a re-install from scratch, after having backed up any meaningful or useful DATA on the disk. I can count the number of times I actually needed to reinstall an OS in the last 15 years without taking my shoes off. The previous 15 years of experience before 1995 don't count as at the time OS's were much simpler.... jaclaz

WHICH link? The latest is 1.7.10 Beta J, available here: http://www.msfn.org/board/index.php?showtopic=144214 WHY would you want a (more) outdated version? jaclaz

I beg your pardon? The Y-Cable has one USB "A type" connector to which BOTH the power (+/- 5V) AND the USB serial wires are connected and another one that ONLY has the power (+/- 5v) wires connected. So you will never actually "connect" the USB drive to two PC's at the same time. The only "risk" is that you will be grounding together the two PC's. This is normally NOT a problem (example two desktops) but it may cause in certain VERY RARE cases (two laptops or one laptop and one desktop) a "ground loop" (since desktops are normally grounded and laptops are not). The theoretical max output of a USB port is 500 mA (usually a port provides slightly more than that) To give you some actual data, some (but not all) 2.5" disks do sport on their label the actual current needed. This is usually slightly in excess of what is actually needed. Seagate Momentus 5400.4 120 Gb -> 0.508 A (i.e. 508 mA) Hitachi Travelstar HTS541080... 80 Gb -> 1.0 A (i.e. 1,000 mA) Hitachi HTS541616... 160 Gb -> 700 mA Samsung MP0402H 40 Gb ->0.7 A (i.e. 700 mA) Fujutsu MHV2080AT 80 Gb ->0.55 A (i.e. 550 mA) Of the above, #1 will most probably work with a "normal" USB cable, #5 may, #2, #3 and #4 will NEED the Y cable. (or an external powered hub, some do give much more than 500mA) jaclaz

WHICH manual? I would have thought that point #7 of the READ-ME-FIRST: http://www.msfn.org/board/index.php?showtopic=143880 is clear enough. jaclaz

For the record, it is Creative Commons and NOT GPL. (as mentioned in the already linked to thread) jaclaz

Yep. That's what I was talking about AFAIK "we" don't have such an automated method/app , but before or later someone may come up with one. jaclaz

That's a good thing, as otherwise you would have to pay me a small fee for the intellectual property of the idea. If I get it right, your customers have normally only two choices: perfection throw away an otherways good printer an buy a new one I thought you were also prone to quick and dirty hacks.... http://www.msfn.org/board/index.php?showtopic=144426&st=9 jaclaz

Well, but *somehow* the MS guys must create this "fully configured image" , even if they do it by typing each single byte , there must be *some* way they create it, so the question is: I presume it is just a question of time before someone finds a way... jaclaz

If it could boot up, I wouldn't be posting the question here, eh? Bolding, like beauty, is in the eye of the beholder. Well, also if you had enough knowledge to actually run a PC repair shop you wouldn't be posting here....(and wouldn't also be using WAREZ) jaclaz

Like using WAREZ? NO, you did not. If you had you would have found a zillion threads where people asking about Hiren's have been told to read the Rules: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules jaclaz

Well, to be picky , I would be curious to see the license of the MS DaRT too... jaclaz

To be fair you didn't explain anything before, you may have "announced it" or "stated it", NOW you explained *somehow* *something* But still it is not an explanation, it's a simple report about why it was disabled, and doesn't really explain why "SP (levl N) can ONLY be integrated in a fully configured DVD with N-1 level". A possible explanation goes something like : jaclaz

The difference that you mention is COMPLETELY unrelated to the problem. You have stick "A" WRONGLY partitioned/formatted (which may also mean that it works on other 99 PC's but not on that one) and stick "B" PROPERLY partitioned/formatted (which may also mean that it works on that particular motherboard and not on another one). It is also possible that the BIOS of that motherboard behaves differently because of the size of the sticks, and/or because of they way they are set in factory (fixed/removable) and for a number of other reasons. A number of possible solutions have been already given in the present thread, and there are other ones. If you wish some help on the issue post the MBR and PBR of bothe the non-working and of th eworking stick, and I'll have a look at them. jaclaz

Maybe, just maybe, something like these could work? http://www.codeproject.com/KB/system/registryasxml.aspx http://www.codeproject.com/KB/XML/registryxml.aspx Or maybe good ol' Registry Viewer: http://paullee.ru/regstry.html http://translate.google.com/translate?u=http%3A%2F%2Fpaullee.ru%2Fregstry.html&sl=ru&tl=en&hl=&ie=UTF-8 jaclaz

What you report is VERY strange. kDn is usually VERY reliable in his posts about grub4dos. Anyway this has NOTHING to do with WinsetupFromUSB, it may be grub4dos or syslinux problem, and should be troubleshooted in the appropriate place. jaclaz

Provided that the ink in the "waste tank" is still liquid (otherwise you need to use some kind of solvent, you get a piece of paper napkin, you roll tightly, you wrap it in some kitchen plastic film, and put the tip of the small and long cylinder you created touching the inside of the "waste tank" or of the "sponge". Then you go for a walk, have some fun, take a nice cup of coffee, whatever. Once you come back, you will find that a conspicuous quantity of the ink will have "migrated" to the paper napkin without a single drop of ink spilled anywhere (thanks to capillarity). Throw away the napkin and make another one. Repeat until everything is clean. A long time ago I had a number of Canon printers, B/W, A3 size that had a separate reservoir of ink connected to the print head (cannot remember the exact model, some 15 years have passed and I am getting lold and forgetful ... ) that did have a tendency to "waste" lots of ink, with this method I was able to clean them periodically before things got out of control, smearing ink everywhere... jaclaz

There are several ways, copying a file to the internal hard disk may be one way. A simple conditional check would be enough WARNING! PseudoCODE: find /somefile.xyz && <do something> find /somefile.xyz || <do something else> It would also possible to put directly a signature on some sector of the hard disk, but it is more prone to errors, and it makes thing complex or could create some incompatibility with something else. There could be a "reversed" way, i.e. write a file on the USB stick *somehow* identifying the PC on which it has been run and have *somehow* grub4dos check this list before choosing the booting entry....:usnsure: Please note that if you go for the "last choice", until you don't delete that file you won't be able to re-install (if unfortunately needed ) from a USB stick setup this way. Typical line of reasoning of the "inexperienced user" if he/she actually has free access to the USB stick : the stupid PC doesnt work I will re-install Windows .... this stupid stick doesn't boot let me re-format it AND run on it any stupid random app I have around it still doesn't work... Phiiilster....! ...and you'll have to prepare another stick and delete the file before being able to re-install Please also note, that the solution has to take into account also multiple internal disks, and what not, to be - as much as it can - "foolproof". jaclaz