jaclaz

About the full-screen problem, I think you can use the shortcut properties to make a DOS app running full-scrren, or good ol' .pif files. Would this work on Win9x/Me? http://windowsitpro.com/article/articleid/...rent-state.html or maybe there is a similar 9x/Me utility? jaclaz

I guess you should look at topics like "escape quotes" or "escaping special characters": http://www.robvanderwoude.com/escapechars.html http://www.ss64.com/ntsyntax/esc.html jaclaz

Which you aren't going to share , so that maybe in the future another user may save that hour or two? jaclaz

Sure, it can happen in some cases. The general idea is to run first CHKDISK without parameters, no changes possible as it will be a read only scan. Check which kind of error(s) it detects and then decide whether going on with /F or /R parameters. But the point is a bit different from how you posed it. Normally, CHKDSK will repair a filesystem, WITHOUT damaging "GOOD" data. In some cases it can "damage" some data but the "damaged" data was NOT "GOOD" data before CHKDISK was used. I hope you appreciate the not-so-subtle difference, though maybe put in a not-so-clear sentence. In other words, it is possible that after CHKDSK usage with the /F or /R option some data is missing, but the missing data was not damaged by the CHKDSK run, it was already damaged or missing before. The "standard" procedure for "accurate" data recovery is: 1) Image the drive as RAW 2) make a copy of the image, for safety 3) try fixing the drive 4) if failing, restore the image to drive and loop to 3) using another approach With this approach it may be possible to recover "bits and pieces" of the damaged files, very, very, very rarely a whole file. jaclaz

Hmmm, that's strange, I have changed the "command lines" inside it in the past with no errors, see here: http://www.911cd.net/forums//index.php?showtopic=18650 How did you try editing the .bin? Can you post the line that "normally" works? However, I am now not so sure to understand your setup, the CD-ROM is also USB? jaclaz

NO need to worry, your drive appears in exceptionally good state. The "analysis" is carried by comparing the values of your hard disk against the data collected by the site over time from users like you that tested their hard disks. It's a kind of "statistical" data, suffering, as most "pseudo-statistical" data from the main error these kind of data may suffer of, sampling error. http://en.wikipedia.org/wiki/Sampling_error Basically, statistical data is more accurate as much you lessen the sampling error (or corrections are introduced in the data). Example: your computer shows that has been powered on for less time that the average of samples. If it's a relatively old model, and you bought it new recently, this can be a valid explanation. But if a relatively high number of the other samples against which your data is compared were posted by people running thir PC 24/7, it could be another valid explanation. On the other hand, if a relatively high number of the other samples were coming from, say, part-time office users, that only run their PC 4 to 6 hours per day, and you are running it 24/7 it could be more difficult to find a valid explanation. The accuracy of such comparisons without the details of the sampling criteria (and corresponding classufication of the data you supplied) and/or number of samples is very, very, very low. Anyway, "common sense" applies also to senseless data, you have 99 instead of an average of 100 on two of the "warnings", and 92 instead of 100 on the third one. To give ANY, even minimal, relevance to the warnings, it would mean that the analysis has an accuracy below or around 1% for the first two, which is mathematically and logically impossible, and below or around 8% for the third, which is possible, but very, very, very unlikely. If you had results like 50/100 or 32/100, while there would still be no concrete reason for being preoccupied, but you might have wanted to carry on some more investigations. http://www.humorsphere.com/simpsons/homer-simpson-quotes.htm S.M.A.R.T. itself is theoretically a predictive algorithm attempting to produce a preventive warning BEFORE disaster strikes, but in "real" world, Murphy's Laws will ALWAYS prevail. Real world field reports assign a good reliability to SMART predictions only for a limited number of parameters/errors, but overall, a very low one, expecially on single drives. This one is AFAIK one of the most recent study on a very large sample, and possibly the only one with such a large sample: http://labs.google.com/papers/disk_failures.pdf jaclaz

Hmmm, use with GREAT care, that is something that may work in a very few number of cases, it's not the "overall" solution, worth a shot ONLY after everything else has failed, as there are quite a bit of probabilities to deepen the problem or cause another reason of malfunctioning. If I were you, first thing I would try to take the drive out of the USB or firewire or whatever external case and connect it directly to a PC through the ATA or SATA connector, just to make sure it is not the external case controller. Then I would try checking it with the Hard Disk manufacturer diagnostic tool or mhdd: http://hddguru.com/content/en/software/2005.10.02-MHDD/ Then I would try running again CHKDSK from command line or Recovery Console. Then again, I wold try running TESTDISK on it: http://www.cgsecurity.org/wiki/TestDisk Of course the two last steps only if there was some success with the previous ones. jaclaz

About the nliting process, it may be that you've removed too much things, cannot say. To install on notebook that has no boot from cd support, it is however recommended to use a floppy with any of the programs able to add the booting capability, thus booting directly the CD: 1) grub4dos: http://www.boot-land.net/forums/?showtopic=5187 2) BCDW - actually the BCDL inside the BCDW download: http://bootcd.narod.ru/index_e.htm 3) SBM (Smart boot manager): http://sourceforge.net/projects/btmgr/ If I were you I would try using BCDL. jaclaz

You do not "add" FILE.TXT to startnet.cmd you add the line: inside startnet.cmd, with notepad or other "pure text" editor. this invokes diskpart using the FILE.TXT as a series (or batch) of commands that will be executed automatically. FILE.TXT, with the contents of the previous post or your custom ones, must obviously be in the same directory of startnet.cmd. jaclaz

Very simplified: the first character in a cell deteremines the type of the data in it. "Canonical" way, input: Working, alternative way, input: jaclaz

@TranceEnergy NO intention whatsoever to offend you in any way, believe me. You just need to read these five pages: http://www.robvanderwoude.com/redirection.html http://www.robvanderwoude.com/redirexampl.html http://www.robvanderwoude.com/condexec.html http://www.robvanderwoude.com/ntfor.html http://www.robvanderwoude.com/ntfortokens.html To be able to understand the batch files, only the first three if you just want to understand the ones by Yzöwl. As soon as you have the time for doing so, you will see that everything will become clear, why the batches did not work for you, and how they can be changed to make them work. jaclaz

Quite strangely, I happened a number of times to experiment, here, or on boot-land or on 911CD, the same problem you describe with my Opera, but in my case, a "reverse" one, it has always been due to "long" lines inside [ code ] [ / code ] tags, changing them to [ codebox ] [ / codebox] tags solved the problem. jaclaz

Sorry, we were cross-posting. My snippet is not intended to delete anything. It is ONLY intended, if token 2 equals to "File" AND token 3 equals to "0" to output the number of bytes. If the output of the DIR command NEVER has "File" as token 2, the variable %Totalbytes% will never be SET. The (better) lines from Yzöwl use the FIND utility to search for "0 bytes" in the output of Du /q, if this output does not contain "0 bytes" it won't do anything, viceversa, if "0 bytes" is found, it will Remove the Directory. In both cases no output will be displayed. jaclaz

If I may , you seem to have a "wrong" approach to the problem. The idea is not that one posts a code snippet and it will work "as is" on any system, with any settings, whatever. The snippet works on my Win2K system, Italian. The idea is to give an example that you should study, understand, and if needed adapt, integrate and modify to your situation, adding error checks, etc. Did you do exactly what I suggested before? i.e. creating the Y:\full directory and putting in it an empty file and an empty folder? Then running from command line the "simple" command? Or did you just copied and pasted the snippet and ran it? Testing the snippet by Yzöwl, did you simply tried before the single commands from command line, like: Du /q "C:\test" Of course this is my personal take on the matter, see also the reply I gave here: http://www.msfn.org/board/Batch-file-to-ed...nf-t122652.html I mean, if I read someone writing something like: I see four possibilities: 1) ALREADY know what that sentence means and what "redirection" means 2) try and find some documents/example to understand the sentence and what "redirection" is 3) ask to the OP : What is "redirection"? What do you mean? 4) This kinda stuff is too much for me, I give up You seem to have chosen a fifth way: 5) Ignore whatever the OP wrote, just copy and paste the lines and see if it works..... jaclaz

Everything OK on Opera, too. jaclaz

Try this: 1) create a New folder, say Y:\empty 2) create a new folder, say Y:\full 3) copy any file(s) to Y:\full 4) Open a command prompt and give in it this command: DIR Y:\empty 5) now try with DIR Y:\full See the difference? Now, try runnig this: @ECHO OFF FOR /F "tokens=1,2,3,4 delims= " %%A IN ('DIR Y:\full') DO ( IF %%B==File ( IF %%A.==0. (ECHO NO files) ELSE ( ECHO %%A File ) IF %%C.==0. (ECHO NO bytes ) ELSE ( ECHO %%C bytes ) ) ) The problem with this approach is with sub-subdirectories, i.e. if there is in the folder: - no files - a subfolder - files in the subfolder the program won't work correctly, but since you actually need only to check if the total is 0 bytes, you can use the DIR /S like in this: @ECHO OFF FOR /F "tokens=1,2,3 delims= " %%A IN ('DIR /S Y:\full 2^>^&1') DO ( IF %%B==File SET Totalbytes=%%C ) ECHO %Totalbytes% bytes IF %Totalbytes%.==0. ECHO It's safe to delete the above still needs to be tested, (the redirection is needed for completely empty folders, in which case the DIR command will return a "File not found"), but you should have a base to work on. jaclaz

Yep, I understand that, what I am missing is what are you asking for: Q: A pointer in the right direction? A: Given Q: Which utility to use from batch to edit a .inf file? A: Given Q: How to edit a .inf file ONLY with a batch? A: Writing your own batch to read and write .inf files, a (read only) example given. Q: How can I give input to a batch? A: ECHO We need some input from you: SET /P TheInput= Please type Workstation name CLS ECHO Thanks, you typed "%TheInput%" A much more complete answer is, again, on the given site: http://www.robvanderwoude.com/batchfiles.html http://www.robvanderwoude.com/userinput.html Q: Can you teach me the batch file commands/language? A: No, sorry, but it's out of the scope of the thread/board, there are a number of tutorials and online documentation, including the Rob van der Woude site I already pointed you to, "choking full" of examples Q: Will you write the batch for me? A: Hmmm, no, I will gladly try and help you with snippets like the above one, or try and help you for anything that is not really basic (if I can ). Don't take it the wrong way , but to me this thread appears a bit like: Q: I'm hoping to drive a racing car, what should I do? A: You will need to take a driving course and obtain a racing license, here is a link to a good school: ............................... Q: Okay, but actually I want to start the engine, where is the ignition key? A: jaclaz

Just an idea, but maybe the 9x version of the Universal Video Driver: http://www.boot-land.net/forums/?showtopic=2325 http://www.geocities.com/bearwindows/vbe9x.htm is worth a shot for a higher resolution. jaclaz

...and the code in mine does This is the relevant snippet: :: List drive letters for network drives FOR /F "tokens=2" %%A IN ('NET USE ^|FINDSTR /R /C:" [A-Z]: "') DO SET BUSYDRV=!BUSYDRV!,%%A :: Remove leading comma SET BUSYDRV=%BUSYDRV:~1% :: Remove backslashes SET BUSYDRV=%BUSYDRV:\=% jaclaz

There have been reports of "strange" problems with USB drivers/bus (and not only) when some "upper filters" or "lower filters" are enabled (or disabled), Daemon Tools is just an example, not necessarily the "culprit", usually it is a conflict, usually "triggered" by an erroneus install or uninstall routine. Google for: or similar keywords, and you'll get the idea. It's one of those problems for which unfortunately there appears not to be a definite cause and a definite fix, everything you can find says in layman terms, more or less: jaclaz

I'll try again: (bolding is mine) No poor, innocent .inf file will be harmed in the process. jaclaz

First example: boot.bin is seeked at .\Source Second example: "Microsoft Corporation.img" is seeked at .\test My bad I had a brain fart, sorry. Correcting my previous post, just to avoid that people may get the wrong info. jaclaz

Does this help? http://www.ss64.com/nt/sc.html jaclaz

You may find some source of inspiration (or peruse my code ) in the freedrv2.cmd script. Originally posted here: http://www.911cd.net/forums//index.php?showtopic=21965 http://www.911cd.net/forums//index.php?sho...=21965&st=6 jaclaz Freedrv.zip

If it is a missing driver, doesn't matter whether SCSI or SATA, the error should be 0x0000007b as well when booting from CD. But the "first part" of Setup should run, otherwise you wouldn't have ever a chance to press F6 to load the drivers from floppy. I am afraid it appears to be something "hardware", cannot say what. A few hours of memtest+: http://www.memtest.org/ won't make any harm anyway. jaclaz