jaclaz

Check if this works: http://www.msfn.org/board/solution-seagate...-page-2093.html (if the cable is that one, of course) From other experiences with Nokia software, it's a toughie and it is very difficult to really uninstall it, it may be faster if you could try the linked to driver on a PC to which Nokia software was never installed. jaclaz

Yes, the problem is that there many versions of the "real/original" Nokia cables and countless versions of "fake/compatible" ones. If you buy a "real" TTL converter (and read the specs ) you have something that is meant to do this work, if you get a CA-42 it may be good or it may not, and you have no way to know in advance. My two cents (already spent several times): http://www.msfn.org/board/solution-seagate...-page-1691.html jaclaz

Simply that everyone has to find "his own" way and use whatever he sees fit for his particular needs. "Newer" is not ALWAYS "better", "more features" are pointless if you don't use them. On the contrary, if you have a need for a feature that is missing in whatever you are using, and the new version has it, do upgrade. I.E. I was just trying to point out that in your sentence: the "so" is not an "absolute and always meaningful" logical consequence: http://en.wikipedia.org/wiki/Logical_consequence (the fact that it might be true in this particular case doesn't mean it is always true) As well, most of the talks here are just personal opinions, the topic being Galahs needing or not to update an app he does not use because of the recent "insecurities" found. I personally find unlikely that Galahs is exposed or "more" exposed because he DOES NOT USE a previus version of IE than he would be by NOT USING a more recent version, other members have a different opinion and suggest to update to IE8 anyway. Both ideas seem like plausible , as it seems to me there is no definite "absolutely valid" answer, and it's up to Galahs to choose what to do. jaclaz

It is possible that a sensor for the motor being up and running is malfunctioning, but the only thing you can do is to check and re-check the connections, AFAIK. The contacts may have been "flatted down" when inserting the card or strip of plastic. See report by beinthemiddle here: http://forum.hddguru.com/tutorial-resolve-...t11040-160.html jaclaz

Another attempt. Try using this example file (editing of course the setting you wish to have BUT without adding any section - and commenting out the ISA card entries): http://www.intel.com/support/network/adapt...b/cs-008268.htm and or double and triple check with this FULLY COMMENTED Windows 95 MSBATCH.INF: http://www.xs4all.nl/~rjnoe/0/pc/soft/win/setup/msbt95a.txt Double check these, too: http://www.uv.tietgen.dk/Staff/Mlha/PC/Soft/WIN/95/setup.htm http://www.uv.tietgen.dk/Staff/Mlha/PC/Sof.../95/msbatch.htm jaclaz

I guess that introducing the concept of "good enough computing" is pointless .... However: http://www.msfn.org/board/good-enough-computing-t133835.html http://www.msfn.org/board/good-enough-comp...35-page-14.html Additional: http://www.boot-land.net/forums/index.php?showtopic=8898 http://www.boot-land.net/forums/index.php?showtopic=6874 jaclaz

@kenppy As said on NT based OS .bat or .cmd is the same, .bat is considered "outdated" and .cmsd is advised, this is because NT based systems do execute BOTH .bat and.cmd whilst DOS/9x/Me systems ONLY execute.bat files. Since the syntax can be different it's a form of "security" setting that avoids a batch file created for NT systems to run on 9x/Me ones. MrJinje has kindly explicited , adapting the procedure to your case, what you should have found by yourself had you read the links I gave you. Basically in the Registry there are settings for the "riight click" or "context menu" for each "kind" of object, among which the "Folder" one, that can be customized. What the procedure you described did in XP was simply that of adding this settings in the Registry. The links I gave you explain the basics and a small program that should replicate the behaviour. What MrJinje posted is a way to have these settings entered in the Registry by using a .reg file that you can "merge" to the Registry. Another app is Wassociate: http://www.xs4all.nl/~wstudios/Associate/index.html (though cannot say it works with 7, it's site and help further explain the way this associations work) A small note: a batch file by default can "index" only 9 parameters passed to it: %1 %2 %3 %4 %5 %6 %7 %8 %9 thus should for any reason the folder you have be "nested" in a path with more than 8 spaces, like: C:\My Programs\whatever main program\the specific program title\data files\main data directory\ the original batch won't work. By using %* instead you get ALL parameters. The added /D to the CD command allows to change Drive, without it the original batch will work only if the directory is on current drive. jaclaz

I wouldn't "count" on it, though. No need to close anything, we know it's solved, but people may want to add something useful in future or ask questions about the procedures you followed. jaclaz

I would guess we are talking about RYU81's one... jaclaz

Mind you ONLY my personal view on your program/idea, which most probably is very good , but I simply cannot bear it. I am speechless , and obviously . I hadn't thought that Rule #13 was so flexible. And anyway: it looks too much like BIG BROTHER to me. And "Affiliate" marketing.... jaclaz

Just to add some fuel and revive this otherwise self-extinguishing fire : http://www.jsware.net/jsware/iewacky.php5 jaclaz

I guess that what Yzöwl was saying is that .bat files are a "historical" remnant of DOS/Win9x, since NT batch scripts use a "better" engine (cmd.exe instead of command.com) and should (though not compulsory) use the .cmd extension. The snippet you posted does not make much sense (to me at least), what is the scope of the CD %1 %2 etc? to get a directory name including spaces? The DEL command when used in a batch does NOT need for confirmation so the whole point of feeding to it through ECHO a "y" is pointless. I would write this: as CD /D %* FOR %%? IN ( .crc. .log. .m_p. .ger. .inf. .lst. .log .plt .idx .tst ) DO DEL *%%?* If I get it right you want to add it to a contextual menu for the object "Folder" or am I mistaken? I think that on 7 the add a context menu entry in Registry hasn't changed: http://www.codeproject.com/KB/cs/appendmenu.aspx http://windowsxp.mvps.org/context_folders.htm jaclaz

That's good , as I also don't believe myself, though you found a rather unpolite way to express it. The whole point of the "unsure" emoticon was that I wasn't and am not really sure about it. Yep, but he said that here: http://www.boot-land.net/forums/index.php?showtopic=1508 on Feb 22 2007, a little less than 3 (three) years ago, and he disappeared since. He was last "seen" on Jul 7 2007: http://www.boot-land.net/forums/index.php?...ic=2566&hl= So, IF it is possible (unlike all known previous attempts) to add the Windows 98 SHELL32.DLL and EXPLORER.EXE WITHOUT adding of the IE bloat, noone - exception made for the mere declaration of intents by Winimize you quoted - seems like having attempted it AFAIK. Does it sound better like this? jaclaz

Your report is a bit "confused/confusing", but thanks for it. You seem to fail to attribute the right "focus" of the problem: it has NOTHING to do with the actual sticks, it is all about the way a given motherboard BIOS behaves. In other works the SAME stick "normally" partitioned/formatted with, say, the HP utility may boot allright on 99 motherboards and fail on the 100th. Well, here you missed a point, by definition jaclaz is always right , some motherboards will have the "switch" at 512 Kb, some at 1 Gb, some at 2 Gb some may not have it completely. Cheers. jaclaz

Good to know we have yet another happy bunny, jaclaz

NO, but I don't think anyone even attempted it. I mean, the point of Mindows is to create a Minimal 9x, if you use the 98 shell, you'll also have IE and all the bloat coming with it. While making it a "full" 98 is out of the scope, maybe it is possible to only selectively make a particular app requiring Win98 shell32.dll work. Something like what was done by FDV for NT/2K: http://www.msfn.org/board/nt4-explorer-xp-t138242.html only the other way around. jaclaz

I guess the bolded part is exactly to avoid a continuous "running after" the new releases: jaclaz

The modified NTDETECT.COM simly "loosens" some restrictions apparently introduced in SP2, it is nothing but a SP1 version of NTDETECT.COM, so you can use it on CD as well. jaclaz

Additionally, if you use dsfo/dsfi (DSFOK package) you can use my batches: http://www.boot-land.net/forums/?showtopic=3191 http://www.boot-land.net/forums/index.php?showtopic=5000 http://www.boot-land.net/forums/?showtopic=2362 for inspiration about the batches you need to write. Another set of maybe useful utilities for more "advanced" chores is of course the findpart set of utilities: http://www.partitionsupport.com/utilities.htm jaclaz

There has been a misunderstanding: http://www.sparkfun.com/commerce/product_i...products_id=449 Let's see if I can clear it. There are two different "TLL" levels standard, a "5V" and a a "3.3V" (sometimes called "2.8V") one. http://www.interfacebus.com/voltage_threshold.html The hard disk "wants" or "likes" the 3.3V ones. A converter can be: powered at 5V and output a 5V TTL level signals <-this WON'T work powered at 2.8V÷3.3 and output 3.3/2.8V TTL level signals <-this WILL work powered at 5V and ouput 3.3/2.8V TTL level signals, or more generally powered at ANY voltage and output a 3.3/2.8V TTL level signals<-this WILL work powered at 5V and ouput BOTH 5V and 3.3/2.8V TTL level signals, or more generally powered at ANY voltage and output BOTH 5V and 3.3/2.8V TTL level signals<-this WILL work if the HD is connected to the "right" TX/RX" of the converter That particular converter you used/got "autoswitches" output TTL level based on the voltage it is powered with. In other words it has an "advanced" feature that turned out as a problem in your case. jaclaz

Just for the record. Partition Wizard: http://www.partitionwizard.com/ Wayback Machine : http://web.archive.org/web/*/http://diskman.dyndns.org/ http://web.archive.org/web/20040604112945/...dm4/manual.aspx http://web.archive.org/web/20040604115216/.../reference.aspx http://web.archive.org/web/20040605000122/...4/examples.aspx jaclaz

Most probably the laptop has a SATA drive, for which you need to integrate a driver (or check if in the BIOS you can set the drive to "IDE" or "Compatibility mode" or something like that, most probably you have now set it as "AHCI"). jaclaz

Well, it depends on the actual board you have, if you have a 5V powered converter you use the Red wire, if you have a 3.3V powered one you use the Orange, I would have thought it was obvious that the procedure has to be adapted to the actual hardware one has, as there are so many variants of the converter circuits it's simply not possible to cover all of them, some will work allright with practically any voltage between 2.9 and 6 V, some are more "picky" however, BTW the original Gradius guide uses a 3V battery jaclaz

Good, happy bunnies are better : http://www.msfn.org/board/cant-access-repa...27-page-10.html Hmm, maybe the BIOS looks for an active partition and exchanges hd order? Well, no, they are actually different, if you check first one it's Entry #1 has "00" and the second one has "80" jaclaz

Really? I don't think the actual problem is Victoria, but rather Windows 7 that has some limits when it comes to "low-level" access. You would save lots of time if you could borrow a "normal" XP running PC from a friend or the like. You must understand that this whole "business" of bricked drives has some aspects of "magic" or "hidden secrets", the less variations you introduce, the more the probability that the "spell" works. You do not need a "self built" interface, you can buy a "real" interface or use a TTL USB cable like the Nokia CA-42. The main thread: http://www.msfn.org/board/117-t128807.html is full of examples on where to find both a "real" converter and how to check/connect several models of "Nokia" cables. If, from your other post: http://www.msfn.org/board/seagate-barracud...-page-1180.html yuor BIOS does not detect the drive it may be a BSY state one. In any case, you need NO firmware update, or at least not for recovering data, the firmware upgrade is useful to avoid that after another 320 log entries the drive re-locks itself, and is actually STRONGLY advised NOT to attempt a firmware upgrade before having a safe backup opf the data. You can try UNbricking the drive allright, in the worst case it won't work (because the problem is a faulty PCB), but in any case (unless of course you "fry" it with overvoltage or shortcircuits), NOTHING will happen to your data (meaning that a data recovery company will nonetheless be able to retrieve it), as well switching PCB's with another drive is NOT advised. (and since you need one exactly of the SAME series it is not even easy to put in practice, as finding a compatible donour might become a nightmare). Check also the CarterinCanada guide: http://www.mapleleafmountain.com/seagatebrick.html and this one: http://sites.google.com/site/seagatefix/Home they are both extremely clear, besides the "main" thread. jaclaz