jaclaz

What about reading the help AND the link I posted earlier? http://diddy.boot-land.net/grub4dos/files/install_windows.htm#windows1 You: DO NOT want a line like C:\grldr.mbr="Grub4Dos" in BOOT.INI DO NOT want a file C:\grldr.mbr DO want a line like C:\grldr="Grub4Dos" in BOOT.INI DO want a file C:\grldr Then, you DO NOT want (when experimenting) a menu.lst file BUT you use command line instead. WHEN you add the set of commands that you already tested on command line to a menu.lst entry you DO NOT need the final "boot" command. WHICH exact version of grub4dos are you using? (among the two I suggested you, NOT the one you had before) Try again chainloading directly grldr (and NOT grldr.mbr), cannot say if it will change anything, but let's first start with the "proper" way, OK? If 0.4.4 2009-16-10 doesn't work, try with 0.4.5c-2012-06-19, or viceversa. There could be an incompatibility with the NT 4.00 NTLDR (but I cannot recall anything about it ) just for test you can replace it with *any* NTLDR from Windows 2K or XP, that are all tested. It could be an issue with the (old) version of NTFS filesytem NT 4.00 uses, since you have a floppy, try putting a copy of the grldr on the floppy (still for experiment only). jaclaz

Just in case: http://dictionary.reference.com/browse/only Of course having a line in batch longer than 2047 characters is very common, as an example, you cannot have this command: DIR /B C:\a senselessly long directory name containing\another pretty much unusefully and stupidly named directory\which is nothing but a container for another directory that contains at least another directory\which in itself is a container\possibly the matrioschkas were not invented by the good Russian guys, but were originated in Poland\but actually the idea of a path is that of being easily accessible and normally the contents of a file goes inside it and not in it’s tiitle nor in the path to it\though of course everyone has his (or her) right to freedom I find it very rare than any NT4 or Win2K (please read as Windows 2000 Professional Edition or Windows 2000 Server Edition) user has ever seen in real life a longer than (say) 200 (at the most) command line – nor I have ever seen a command line tool that – when enclosing ALL available parameters and switches has ever reached that length – so all in all if you use absolute paths to call a tool that is residing on a 256 long path and having BOTH a source and target among it’s parameters – you manage to get at the most WHAT 800 characters – let’s double it to 1600 and you still have 400 + 47 characters before hitting this limit\just for your info at this point (including spaces) we are around 1300 characters before this backslash\so we can continue writing senseless directory names that noone will ever use (in his right mind) in real life if not to prove a completely senseless point about the max length of the command line that the NT and Win2K will be able to accept\you see I made my point in much less than 2047 characters so I have to continue writing this \I wonder why the good MS guys instead of saying it’s by design which is what they normally do on actually relevant bugs took instead the time to fix it – as I see it this happened only because they found this by chance in the source code of CMD.EXE and in order to get a pat on the shoulder or however make himself more visible the anonymous programmer which found it managed to make a bug submission and solve it working properly in NT and 2K. jaclaz

On other news, Meanwhile in Italy: http://www.macworld.co.uk/digitallifestyle/news/?newsid=3404468&pagtype=allchandate Meanwhile in Cupertino: Back on topic, I don't remember this one being cited http://seattletimes.com/html/businesstechnology/2019168601_microsoftballmer16.html IMHO this is not LSD or peyote, it is downright Salvia divinorum : http://en.wikipedia.org/wiki/Salvia_divinorum jaclaz

The idea of the original "fix" guide was that a given (very minor) issue in the firmware made a drive data unreadable. What happened is detailed and documented, basically the firmware entered in a kind of "loop" without exit. So you have a perfectly "sound" disk drive which firmware has entered a loop. A way was devised (or actually somehow was "leaked" from the pro's) that allows to exit this loop. Since a later firmware has been corrected and avoids the entering in that loop, it is a simple equation: if before the firmware update, the drive bricked itself you have this new equation: Once every possible existing on earth drive (with the initial "bad" firmware) was either "recovered/fixed" or sent back to seagate for replacement or thrown away in despair, people started to try the same fix on *any* drive showing the same symptoms, and in some cases the fix worked (but we have NO idea on what caused the issue and if the "reset" actually fixed it or simply allowed to "tempirarily hide" the symptoms). Compare with Aspirin : jaclaz

Still you don't need the :End label, the implied :EOF is good enough. jaclaz

Well, you should use a newer version of grub4dos. What is recommended (by me) if you are going to use a 0.4.4, is version 2009-10-16 (which is latest 0.4.4 series): http://reboot.pro/16641/ or (better) the newest "Featured" from the grub4dos homepage: http://code.google.com/p/grub4dos-chenall/downloads/list HOW are you loading grub4dos? I will presume like this: http://diddy.boot-land.net/grub4dos/files/install_windows.htm#windows1 You NEVER (when experimenting) use a pre-made menu.lst entry, you use command line, pressing "C" to get to the prompt and entering commands one by one, this is because this way you get feedback from grub4dos related t the last command entered, thus, in case of issues you know WHAT exactly casuses it. Usuallly (but of course in no way "compulsory") floppy images are given .ima extension, whilst hard disk or partition images are given .img ones. Memtest is "easy". find --set-root /memtest.ima map /memtest.ima (fd0) map --hook chainloader (fd0)+1 rootnoverify (fd0) boot The above sets of commands (once tested working become a menu.lst entry as this: (you never need a boot command on a menu.lst as it is implied, i.e. automatically issued if EOF is reached or another "title" entry is foun in the menu.lst) The MS-DOS 6.22 in a hard disk image is more complex. Is it a hard disk image or a partition image? (i.e. is it's first sector a MBR or a PBR)? Assuming the first: find --set-root /msdos.img map (hd0) (hd1) map --hook map /msdos.img (hd0) map --hook chainloader (hd0)+1 boot jaclaz

No. (wrong reason) In the best case, IF a recovery procedure succeeds, what you have in your hands is a half-@§§edly repaired disk, "fixed" along an undocumented procedure that contains, besides a lot of guessing, some (white) magic. The only use of such a disk drive (besides it's utility as a door holder) is - once it has passed both short and long test from Seagate (and if it passes them) as a secundary or tertiary backup media or for experiments, you can't call it "storage" as it's reliability is "unknown" (in the sense of "even more unknown" then that of a new, working hard disk). In order to save some 80 bucks you are going to spend (possibly) some 20 bucks for the tools and spend several hours (most of them in a state of utter frustration). If you declare that you do it "for fun" and/or "for the sake of experimenting" and to learn something new, then it's OK . However, yes , if there is a delay when booting and then the disk is not seen by BIOS it is very likely a BSY state. In practice the BIOS "calls" the device on the end of the SATA cable with the intention of starting a conversation of the type "Hi, sorry if I am bothering you, I think we haven't met before, I am the BIOS of the PC, who are you? A sata disk? Yes? Which make? Which model?" (BIOSes tend to be friendly but nosy ) but the disk has forgotten the handset/earpiece off the hook and what the BIOS gets is a busy tone . We don't have a "tested procedure", only partial reports and a couple links. You should read ATTENTIVELY the Read Me First for the 7200.11 (as some "general ideas" are in common: then the CarterinCanada's guide (again aimed at the 7200.11): http://www.mapleleafmountain.com/seagatebrick.html and finally this thread (and links in it): jaclaz

Yep , It is a (cute ) "thank you bunny" connected to: jaclaz

So, if I get it right, you have your DiamondMax23 (please read as Seagate 7200.12) in BSY state? And it became so during a firmware upgrade performed when booted from CD? And before that the "running in Windows" utility failed? Are we talking of these?: http://knowledge.seagate.com/articles/en_US/FAQ/213911en http://knowledge.seagate.com/articles/en_US/FAQ/210091en jaclaz

This makes little sense. 400 Mb is NOT a "biggish"disk size, you were talking till now of a several Gb one. IMHO what you should try is making a disk of the size you need it using IMDISK "native" allocation and test it in both ATTO and CDM, then make another disk of the same size using awealloc and test it with both ATTO and CDM, then disregard BOTH results of BOTH benchmarks and simply try running that game with one and the other method and choose the one that "feels" better (if a difference can be felt) pr that results more stable. I presume that if the Author of the tool says: it is very likely that there are reasons... jaclaz

You can try with IMDISK to load a small image, extend it and then copy to it the files, it may be quicker A 2x factor between Intel based and AMD "sounds" still a lot, possibly some of the guys with more specific hardware experience might want to comment. jaclaz P.S.: Also, since your disk is biggish, you should try awealloc, compare with the reply that Olof in the meantime posted on the previously referenced thread: http://reboot.pro/17610/

...and are you going to tell us HOW EXACTLY you made this happen, or if you prefer WHAT EXACT bit was the correct one and WHAT other bits are misleading? jaclaz

The Issues might come with some special characters in the filenames. This is a "compacted" version of the two batches you made. Hopefully putting double quotes around %%j will do the trick. In theory having moved the deletion to the subroutine and having linked it to the copy command should avoid the accidental deletion of a non-copied file. @ECHO OFF FOR /F "delims=;" %%i in (List.txt) do ( call testsub %%i ) GOTO :EOF :testsub FOR /F "delims=;" %%j in ('DIR /B *%1*.*') do ( if not exist .\%1 md %1 copy "%%j" .\%1\ &&del "%%j" ) GOTO :EOF jaclaz

If I may, I would set aside the topic of Skydrive. If - for any reason - the images that created the closing of the account were - even remotely - connected to or similar to or viewable as any form of child pornography, I do understand the MS policy, and while I understand how it could be a nuisance for the casual innocent user that sees his/her account shut down, I personally find that it's relevance, when compared with the crime that is supposedly being committed, justifies it. The only observation I can do is that the 48 hours time to provide justifications is too short a time. BTW there is also a procedural issue, under US Law, even if you are a forensic investigator, as soon as you see an item that could be associated to CP, you should stop and call the Police or the Feds, compare with: http://www.forensicfocus.com/Forums/viewtopic/t=9693/postdays=0/postorder=asc/start=0/ jaclaz

No. Meaning that you tried them allright but with the "wrong" approach. or, more simply you haven't tried "hard enough". The essence of tools like WinsetupFromUSB is that through the work of ilko_t a "sub-set" of the possibilities is made "easilily" available to everyone, i.e. in 99.99% of cases it is just a matter of following the instructions and prompts (and knowing how exactly it works and why is totally "optional"). Most other methods and expecially those aimed at PE 1.x's are DIFFERENT in the sense that the PE often needs to be built in a given way, or - in the case of your already made PE - need to be modified. This requires some time to study the methods, understand the processes, troubleshoot the issues. A number of Winbuilder projects do allow booting form .iso (or from .img) with grub4dos, as well there are tutorials for UBCD4WIN: http://www.rmprepusb.com/tutorials/ubcd4win or for a BartPE: http://www.911cd.net/forums//index.php?showtopic=24100 rest assured that they do work, but each one usually needs to be tested/adapted/what not. Generally speaking firadisk based solutions tend to be more easy (but they require machines with a bigger amount of RAM) while Winvblock ones tend to be a bit more "picky". BTW, there is still the good ol' method using the MS ramdisk from Server 2003 SP1, that has worked for years, a typical example being the Sysinternals ERD Commander one. jaclaz

Meanwhile in Australia... jaclaz

My bad , I forgot to escape the ">" with a caret, try with this: @ECHO OFF FOR /F %%A IN ('DIR /S /B *apple*.*') DO ECHO APPLE: -^>%%A This one liner should list all files containing "apple" (case insensitive) in the name and display them on the screen. jaclaz

I have read the post. See if you can spot any difference between : Office 97 installing on Windows 7 failing. Office 97 installing on Windows 2000 on a CF card seen as removable failing jaclaz

All your verb are belong to us. Meanwhile in Cupertino and China: Meanwhile in http://icanhas.cheezburger.com/ jaclaz

Hmmm. Some documentation is inside the "stable" (and not inside the beta). Would this mean that in an attempt to better the tool ilko_t removed features form it? Would this mean more simply that there is no new documentation in the beta's? Why don't you simply try and see if it works with the Beta? jaclaz

First post of this thread, as you were told: http://reboot.pro/17563/#entry161427 jaclaz

Still,it remains a mistery (at least to me) why all your Crystal Diskmark benchmark reports show roughly half the speed Raymond got . jaclaz

Sure it is! jaclaz

You <missing verb> casually unaware of this meme http://ohinternet.com/I_accidentally jaclaz

"pure" RAM testing? http://hcidesign.com/memtest/ jaclaz