jaclaz

NO, these files are only needed on the active partition (the one that normally is C:) io.sys, config.sys and COMMAND.COM are the system files for DOS/Win9x/ME, unless you had a dual boot you won't need them. autoexec.bat and config.sys are, as said, DOS/Win9x/ME files, and they are NOT needed for booting. config.nt and autoexec.nt, are NT files, but they are as well not needed for booting. Please note that if you have different versions of NT based systems, the NTLDR and NTDETECT.COM must be of the LATEST version you have (they are all backwards compatible, but usually NOT forward). jaclaz

Needed files are listed here: http://www.msfn.org/board/index.php?showtopic=33030 And yes you can just copy them over, though I cannot say if the problem will be fixed with just that (I mean, from the report you made there is no way only these files could be deleted, it is possible that you still have some kind of partition corruption) In case a similar occasion happens, do use TESTDISK: http://www.cgsecurity.org/wiki/TestDisk it is VERY good for recovering partition info. jaclaz

Yes, it is possible to replace those files form Server2003 SP1 or later to have added benefits. DO read here, new ideas for both PE and "full" XP: http://www.911cd.net/forums//index.php?showtopic=19333 http://www.911cd.net/forums//index.php?sho...19056&st=19 http://www.boot-land.net/forums/index.php?...ic=1145&hl= jaclaz

Yes, that is exactly what can be done (together with other things) by the MBRfix app linked to before, which runs under 2K/XP/2003. No need to boot into DOS. jaclaz

@Pirates No, Lexar is out of the "game", the post on 911CD I referred to was a sequel to a few e-mails I had with wm_raim, wher he cleared that he was trying with TWO sticks, one a Lexar With Vid 05DCh and Pid 0080h and the other one the GXT with Vid 1516h Pid 8628h. Sorry for the mix-up. Usually the manufacturer of the chip has his own Vid/Pid, when he sells his product to the makers of the flash stick, he gives them an utility to change Vid/Pid to that of the stick manufacturer (if he has one), as a cascade, when the stick manufacturer actually tests the stick he has the option to insert the Vid/Pid (if any) of the Commercial company that has the "Brand" name and that actually sells the stick on the market. Acquiring a Vid is relatively easy and cheap: http://www.usb.org/developers/vendor/ while the Pid is an internal code, that in some cases is "meaningful", i.e. OtI sticks have Pid 2168 if they use chip 2168, Pid 6828 uses chip 6828, etc., but as soon as they developed various versions or "updates" of the chip, it agains loses significance, as an example, if I recall correctly, there is a "F" version of the 2168 and a "G" version with added features that cannot be distinguished by Pid. Given the above it is easy to envision a scenario where Vid can mean: 1) Chip manufacturer (most of them) 2) Stick manufacturer (I think few of them that payed the $2000/$4,000.00 fee) 3) Commercial vendor of stick (I think still fewer that payed the $2000/$4,000.00 fee) About speed, I cannot say, but the reference to 23x on the cnmemory.de site could be related to the 23.1 Speed on the skymedi site? Speed of a flash device appears to be something "unmeasurable" without a standard, however the Ratio between 31.1 whatever for Read Access and 21.3 whatever for Write Access seems just not right Check these: http://www.anandtech.com/printarticle.aspx?i=2549 http://arstechnica.com/reviews/hardware/flash.ars/1 http://arstechnica.com/reviews/hardware/flash2005.ars for a speed comparison and to see how much speed is influenced on size of what you are reading/writing. In your case I think that we fall in point 1) above, where two different commercial companies, valgear with its brand GXT and cnmemory with it's own name offer on the market sticks that mantain the Vid of the Chip manufacturer (and use the chip manufacturer driver for Win98). jaclaz P.S.: Sorry if I am somehow hijacking this thread....

The "particular" CD's hat apparently have more than 800 (or 850, and there are even, very rare, 900 Mb ones) use a technique that is only possible if the SAME files are in several different directories. As said, CDIMAGE/OSCDIMG.EXE or mkisofs can make such disks, nothing really "magic": http://www.msfn.org/board/index.php?showtopic=49821 jaclaz

Wouldn't using DEVCON be possible/easier? http://www.robvanderwoude.com/index.html http://www.robvanderwoude.com/devcon.html http://www.robvanderwoude.com/files/getdevdj.txt or using rundll32 PRINTUI.DLL? http://www.robvanderwoude.com/2kprintcontrol.html To find real devices you can use a "side effect" of the DIR command: http://www.robvanderwoude.com/isdev.html Open a command prompt and try: DIR LPT1: (a valid port) and DIR LPT3: (a NON valid port) and see the difference jaclaz

You are welcome. jaclaz

nlite is for XP vlite is for Vista Homepage: http://www.nliteos.com/ http://www.nliteos.com/faq.html jaclaz

Actually, and just for the record, the "proper" way to store floppies is to make "RAW" images of them. This will make it possible to revert back to a floppy when needed, or use the floppy image in a VM exactly as it was. A very large number of DOS/Win3.x apps needed to be on floppy because some info was "hardcoded" on the floppy itself, possibly in a hidden sector, or in a file that was addressed with direct head/cylinder access rather than through filesystems. A few of the at the time in use copy protection are however more sophisticated than that, some info and related apps here: http://retro.icequake.net/dob/ For normal 1.44 floppies a simple freeware app is Dcopy (DOS) or DcopyNT (NT/2K/XP): http://users.pandora.be/jbosman/applications.html http://users.pandora.be/jbosman/dcopy.zip http://users.pandora.be/jbosman/dcopynt.zip jaclaz

@patchworks As said, I am too a fan of Opensource, I even actually wrote some (in my very primitive batch files) but as you have your point of view: I have my rather more pragmatic one: while substituting MS defrag.exe with an opensource one, is a nice thing and, more important than that, it is pertaining to the OP request, IF the program exists. If it does not, it does not solve the problem, nor does it belong to this thread.... So the answer to my question: is clear (bolding is mine): About this: you might however understand the difference there is between starting a new thread about an existing good app and hijacking someone else's thread with unuseful, unrelated information. And I am begging the pardon of other members if our little exchange of ideas has worsened this hijacking jaclaz

The missing point is that an .iso file, like the one nlite creates, is a FULL IMAGE of a CD. (i.e. it ALREADY contains bootsector, etc.) You don't need to fiddle with you just burn the .iso. If you want a simple, no nonsense app to do so, check one of those referenced here: http://www.911cd.net/forums//index.php?sho...c=18845&hl= IMGBURN, ISOBURNING or BURNCDCC are all good. jaclaz

Probably completely unneeded/unrelated, but maybe this can be of some use: http://www.zeraha.org/content/dload.php?ac...y&cat_id=11 http://www.zeraha.org/dload.php?action=file&file_id=27 (just found it on a rather old bookmarks list and thought I'd share it jaclaz

About the id of the stick chip, see this post of mine: http://www.911cd.net/forums//index.php?showtopic=18804 It seems like the manufacturer is: http://www.skymedi.com.tw/eng-index.html http://www.skymedi.com.tw/products/sk6201.htm and that the same stick is sold as GXT at http://www.valgear.com jaclaz

I don't get it. The screenshot is of a web folder in GMX mediacenter..... jaclaz

If you haven't already completely destroyed data on the drive, TESTDISK: http://www.cgsecurity.org/wiki/TestDisk may still be able to re-build partition table. If you are able to get an access to ntuser.dat, you can try recovering the actual original KEY: http://www.dagondesign.com/articles/window...t-key-recovery/ About: http://www.openoffice.org/ Openoffice.org is now really 99.99% compatible, BOTH on Windows and Linux platform, that would take account for Word and Excel files. I cannot say for Outlook.... You joking, right?: RULES: http://www.msfn.org/board/index.php?showtopic=18408 jaclaz

Only apparently OT, do try the newish Virtualbox, FREE/OPENSOURCE, it appears to be REAL fast: http://www.msfn.org/board/index.php?showtopic=90774 www.virtualbox.org jaclaz

No, unfortunately you miss some studying and learning, see here:http://www.911cd.net/forums//index.php?sho...=17538&st=3 http://www.911cd.net/forums//index.php?sho...=16980&st=8 These Boot.ini entries are "pure nonsense": Read this: http://www.msfn.org/board/index.php?showto...54304&st=13 and ALL links therein. jaclaz

Sure. I am too, but I try to give links related to the topic, not general, unrelated things. I used (and posted a link to) jkdefrag, besides other utilities, a rather long time ago, here: http://www.msfn.org/board/index.php?showto...85812&st=47 Well, my eyes are open enough to read: Though a very nice utility, it NEEDS NT family API's, Win9x/Me are different. Yes. FreeDOS defrag, on the other hand, is known to be buggy, expecially on large volumes. Very good idea, and while you do it, we could plan to live forever happily, together with our flying elephants, but WHAT can this be related to solving the problem swgreed has? jaclaz

Yes, it is possible that the MBR on second drive is missing. http://support.microsoft.com/kb/141702/en-us Boot.ini should be OK, as Arcpath actually should point to first drive (and the second one should become first if the first one is removed), but adding a second entry to boot.ini to experiment should not be a problem, which could however be the master/slave problem. You can use MBRFIX: http://www.sysint.no/Nedlasting/MbrFix.htm http://www.sysint.no/Nedlasting/MbrFix.zip and (optionally) my small GUI for it: http://home.graffiti.net/jaclaz:graffiti.net/index.html http://home.graffiti.net/jaclaz:graffiti.n...X/mbrfix0.2.zip to check and fix the MBR. Still, you might have a problem with disk signature/drive letters assignment when booting Windows. jaclaz

Here: http://www.msfn.org/board/index.php?showtopic=78592&hl= jaclaz

The problem can be: an error of the program you used to create the .iso (WHICH program did you use?) a bad burn of the DVD (ALWAYS use LOWEST possible speed for burning) You should check the .iso BEFORE burning on a Virtual Machine. jaclaz

Interesting, I had thought you were "married" to diskeeper : http://www.msfn.org/board/index.php?showto...85812&st=47 @all Some more links to FREE or LOW COST defraggers and related apps can be found on my post here: http://www.msfn.org/board/index.php?showto...85812&st=22 jaclaz

write a batch and call it from autorun jacòaz

Just to keep things together, it seems like a similar problem was solved, here: http://www.msfn.org/board/index.php?showtopic=83032&hl= jaclaz