jaclaz

NO , they are completely different errors (and causes for it). NO . There can be several causes for the "click of death", most solutions for them they are simply NOT doable "at home", and the others are NOT documented on this thread. You can try applying the "LBA0" fix, not because the fix or problem is in anyway related to the "click of death", but because the procedure may "refresh" some data that may be connected with the clikcking. Unfortunately your only hope is trying at hddguru Forum: http://forum.hddguru.com/ it is possible (but not probable, again unfortunately) that some of the guys over there will help you. jaclaz

FreeDOS Fdisk freefdisk: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/ The whole point on which seems like we are misunderstanding each other is that for the DOS way you make the internal hard disk bootable in DOS, and copy to it the Source files (\I386\ directory) and then run from it the Setup. The USB stick is taken out of the equation very soon, after the files are copied to the internal disk. The method, though awkward and not "easy" has worked for years, at the time it was very common, on a "normal" machine to have DOS, and, to speed up the installation (and being not nagged to insert CD later if some features were not installed in first instance) to copy from the CD the \I386\ directory on HD and run WINNT.EXE from the HD. jaclaz

If anyone has the problem, he should get the already given floppy: http://johnson.tmfc.net/dos/usbdrv.html which contains the same panasonic drivers+a few others (DUSE,Iomega) updated when compared from those in the 2003 article, the ones in the given link on Panasonic site are v2.06, the ones in the given link are v2.15, which should be faster/better. However, this is the reference to get v2.06 and v2.15 and use them: http://www.computing.net/answers/dos/dos-mass-storage-driver-usbaspisys/15261.html jaclaz

Can we have the "classic" skin? jaclaz

I think that one of the "less clear" things in the "Windows business" are Fonts. The information about them is on half of the internet, but often (read ALWAYS) it is not clear. Take this (nice BTW ) page for example: http://www.mydigitallife.info/2008/11/20/h...command-prompt/ And this one: http://windowsitpro.com/article/articleid/...le-windows.html Evidently more or less copy/paste from: http://support.microsoft.com/kb/247815/en-us And the questions are: is there a program that can go through a Fonts directory and point out these characteristics of the fonts? is there any FREEWARE program that can change the charactristics of, say, a fixed pitch font but NOT FF_MODERN to FF_MODERN or a "converter" kind of app? if yes, where is it? Also, can please someone explain what the heck is a "negative A or C space"? jaclaz As a Side note: Fonts that have these characteristics: White Rabbit: http://www.dafont.com/white-rabbit.font Found on: http://www.mydigitallife.info/2008/11/20/h...command-prompt/ Consolas Vista or 7 or Power Point 2007 Viewer: http://labnol.blogspot.com/2007/03/downloa...ts-legally.html DejaVu Sans Mono http://dejavu-fonts.org/wiki/index.php?title=Download Droid Sans Mono http://damieng.com/blog/2007/11/14/droid-s...eat-coding-font Found on: http://blog.wolffmyren.com/2009/02/26/nece...command-window/

What do you mean by IP range? The subnet mask? Or the Lan card IP? Something like this: http://www.robvanderwoude.com/ntfortokens.php You can parse the IPCONFIG /ALL command output. jaclaz

You won't like the answer. You need: to have LucidaConsole (or another TTF font, NOT the raster one) to change page to 1251 possibly start CMD.EXE with the /U parameter You need to have SEPARATE batch file and Cyrillic text. Example copy and paste this in a Notepad or Wordpad and save as Unicode with name "choices.txt": Copy and paste the following in a Notepad or Wordpad and save as "plain" text with name "test.cmd" @ECHO OFF chcp 1251>nul more choices.txt for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "1"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "2"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "3"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "4"') DO ECHO %%B chcp 437>nul Open a command prompt, make sure that you are using Lucida Console. Type in it: MORE choices.txt [ENTER] Now run test.cmd: TEST [ENTER] jaclaz

Have you actually READ the suggested "old" method? http://www.911cd.net/forums//index.php?showtopic=16713 jaclaz

You can tell that guy he could have a career at Seagate. jaclaz

No, I am saying that I did not understand your question, and that the file you posted contains no UNICODE characters, nor Cyrillic ones. Can you post an example (a short Cyrillic name/word)? Read this in the meantime: http://www.chem.msu.su/soft/convert/readme.txt Get the file: http://www.chem.msu.su/soft/convert/ and play with it a bit. are you using (CP866) or (CP1251)? Open a command prompt, type in it EDIT [ENTER] and use the "DOS" editor to create/modify the batch. jaclaz

I don't understand the question. It should actually have a .cmd extension, and it is so short one can post it in a codebox without problems: @echo off cls TITLE: echo 1) Mozilla Firefox echo 2) Internet Explorer 8 echo 3) Media Player Classic echo 4) EXIT :a set /p ans=Enter a number: if '%ans%'== '1' GOTO one if '%ans%'== '2' GOTO two if '%ans%'== '3' GOTO three if '%ans%'== '4' GOTO four GOTO a :one cd "C:\Program Files\Mozilla Firefox" start firefox.exe GOTO a :two cd "C:\Program Files\Internet Explorer" start iexplore.exe GOTO a :three cd "C:\Program Files\K-Lite Codec Pack\Media Player Classic" start mplayerc.exe GOTO a :four exit Can you try beetter explaining the problem (apart the fact that "TITLE:" is hardly a batch command)? jaclaz

Just for the record, unless a multi-sectors third party bootmanager is used, in a "normal" MBR the sectors that make it up are just ONE (first sector of physicaldrive). Since the code has been hopefully fixed by bootrec and the partition is found with /ScanOS, the only missing thing could be: wrong partition type (but it shouldn't actually be a problem) non--active partition (which could be the problem) Of course if the advice: Actually translates to: And this: Actually translates to: It will be hard to know what has happened/is happening. jaclaz

And speaking of XML output , and JFYI: http://www.911cd.net/forums//index.php?sho...23408&st=21 be AWARE of the (hopefully false) positive jaclaz

The 7200.11 uses 38400 8 N 1. Is that board using 3.3V or 5 V TTL levels? You want 2.8 or 3.3V ones. Read this: http://www.msfn.org/board/index.php?showto...807&st=2338 jaclaz

To sum up, we now know that two apps "automagically" created a coaster on your particular setup and a third one "automagically" created a working DVD. We don't know whether it was: a "glitch in the matrix" (which would likely not happen again/be reproducible) an incompatibility of some kind with the media an incompatibility of some kind with the hardware an incompatibility of some kind with your source file structure or whatever a PBCAK So, we have not learned much, apart from something we already knew , that IMGBURN is a very dependable app. In other words, the problem is solved , but we don't know WHY it happened, nor HOW it can be fixed should it happen again. Can we count you in the basket of happy bunnies, now? http://www.msfn.org/board/index.php?showto...28727&st=10 jaclaz

@Ponch Yep, but it is a bit unlikely to happen in real life. Not that a lot of people don't normally tie their hard disks to a rope and start spinning them like mad, only that very few will stand the three ton pull. A common thng that may happen in real life is: the drive is on a table or bench (around 3 Feet high) you, your mate or your pet make it fall to the ground If the data calculated is correct your drive is dead. So, instead of "if the drive experiences shock in excess of 300 Gs" they could well write "if the drive falls from your table", which would be, I presume, more easy to understand. An ever better one may be "if dropped on a hard surface from more that 30 cm". And the moral or lesson in this story is: the Japanese have a clear advantage over us westerners, as they normally use: lower tables tatami carpets under them jaclaz

I did a couple of tests, and that geometry seems allright after all, it means that you partitioned that thingy under an unpatched Vista with Alignment ON, aligned on 1 Mb. So the partition table geometry is "right". the only problem is the partition ID, (which is not a problem it's just a matter of 06 07). You seeem like a lucky guy, as all that is missing appears to be the first sector of the NTFS bootsector. I need another bit of that thingy: dsfo e:\dsfok\hddfull.img -2560000 0 e:\dsfok\last5000.bin Translation: there is a copy of the bootsector as last sector of the partition on NTFS filesystem. TESTDISK should be able to find it, however. http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step http://www.cgsecurity.org/wiki/TestDisk_St...sector_recovery Before fiddling with it, however, do post the last sectors, I will assemble a file for you to merge with the image. jaclaz

Cannot say with Vista RE. jaclaz

Boot from a DOS floppy with any suitable disk utility and check that there is a partition active. jaclaz

The data is very, very strange. 06 00 0 32 33 1023 254 63 2048 234436608 The partition type is FAT16. The CHS offset is that of a small device with 32 sectors. (32+1)*63=2079 and NOT 2048. The file you sent is all 00's apart the MBR. Try posting a bigger chunk of the image: dsfo e:\dsfok\hddfull.img 0 2560000 e:\dsfok\first5000.bin jaclaz

That message seems like coming from the BIOS of the machine that cannot find the drive as BOOTABLE. Are you sure that the HD is in the Boot priority list in BIOS? This may be also due to having NO active partitions in the MBR Partition Table. Have you some kind of alternate boot media? Like: Floppy CD (and a CD burner) USB stick (you will lose the data on it, so back it up) jaclaz

No prob. Definitely they are not the only ones. We have a whole catalog of alternate tricks. But, JFYI, unless I am mistaken, under the terms of the contract I signed, I am in no way obliged to: answer all questions answer questions recommend (or NOT recommend) software attempt persuading anyone (or fail to) over anything prove (or fail to prove) ANYTHING All I do is trying to see if I can help, but I will do it with my methods and at my own pace, take it or leave it, no offence intended, and no offence taken. I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE or mkisofs vs magiciso or whatever, they all seem to me like King Kong vs. Godzilla (and JFYI, the dinosaur can get rid of that grown up chimpanzee with one hand tied behind his back, anytime ) You want MSCDEX.EXE, have it, it's all yours. Now, back to the problem. Let me see if we can sum up the original problem: you made a DVD that does not boot you made it with a custom floppy image you made it with MagicISO The problem can be: in your DVD hardware in your custom floppy image in MagicISO in a PBCAK My first idea was that it was MagicISO or the PBCAK . I simply suggested a way to test if that was the problem, but you have a number of limits in your current environment: no VM no certainty about the DVD hardware From what you report and from results of your tests with Nero, I am starting to really think it is #1 above, and if this is the case there is no need to change anything. Try doing yet another attempt with IMGBURN: http://www.imgburn.com/ using these instructions: http://forum.imgburn.com/index.php?showtopic=1779 and your usual floppy image as boot image. If it's another coaster, I would say that it is a hardware problem, so you can forget everything about mkisofs and it's commands and about MSCDEX vs. SHSUCDX, and even this whole thread, just go to your trusted PC dealer, fork from a few bucks and get a new burner. jaclaz

I wonder which is the difficult part in this: I'll try to translate it: this is alpha/beta software, ONLY people with an adequate DOS background, and specifical DOS driver knowledge should attempt using it the USBINTRO is a 186 page document, you should read them all you cannot expect that anyone will explain the whole 186 pages AND teach you about DOS driver loading on a technical board in order to be able to read and understand the mentioned document you need to have a base knowledge; from the fact you posted: I presume that you miss this base knowledge, that you can only build by reading, googling, and reading again, and experimenting, in order to have the needed DOS background Please don't take the above as "I don't want to help/assist you", but you should be conscious of what you are asking, more or less a complete DOS course, which I presume would take a few days/weeks. jaclaz

Well, the bootrec.exe /fixmbr should ONLY fix the MBR CODE, you must now check the MBR DATA. http://support.microsoft.com/kb/927392/en-us Post the EXACT message you see when trying booting. (EXACT, means EXACT, including CaSe) jaclaz

NO, don't worry, it applies only on USB devices. http://www.msfn.org/board/index.php?showtopic=125116 NO. If that thingy won't work on 2K there approximately 0.000000000001% probabilities it will work on XP. jaclaz