jaclaz

Honesty for honesty, neither have I. Fact is that the "pure-DOS" batch language is so limited that people over the years invented so many workarounds, mostly using "quirks" or "undocumented side effect of some commands" that is nearly impossible to keep track of them, and often not even to actually understand how they work. You need some act of faith and trust them, or you need to test them one line at the time to understand what happens. jaclaz

Which kind of hard disk has that PC? If SATA you NEED to slipstream the appropriate driver to it. (and what you are having is a STOP 0x0000007b) Check FAQ #3: http://www.msfn.org/board/index.php?showtopic=116766 jaclaz

Only to happy to have contributed to yet another happy bunny! http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

If it's allright, I can put together a "READ this BEFORE" post on order to disambiguate the most common requests. I will PM it to you as soon as I hvae put it together, and then - after review - I can post it as a new thread, that you may want to make sticky. BTW, this thread should be made sticky too: http://www.msfn.org/board/index.php?showtopic=133387 The point is slightly different. You can build an interface capable of connecting to (and hopefully de-bricking ) a segate drive with almost ANY kind of electronic junk you have in your basement. (I posted a number of schematics to this effect) The problem is rarely (please read as "never") the actual cable, it's a PBCAK. The LESS the user knows about electronics and installing a virtual COM device in Windows, the MORE he/she is attracted by the CA-42 solution. I am pretty sure that, exception made for a few DOA's, all the cables are perfectly functional, but due to the number of "real" ones, and "fake" ones and different releases, and what not, each one needs to be checked and connected PROPERLY and in some cases externally powered, and each one may have different cable colour coding and what not. We started with: a given OS a given connection app a given kind of hardware and little by little everyone tried: a different OS a different connection app a different kind of hardware which is of course allright , the only problem is the whining about the modified things resulting in a not working result, when the same "error" and solutions to the "same" modifications/variations to the original tutorial(s) have been posted n times. I do understand that this thread has grown to an unmanageable size, but what the heck, half of my posts are of the kind "please read this previous post where EXACTLY the same problem has been solved".... ... I will try to do my best to sum up the common requests and create a sort of FAQ/FGA: http://homepages.tesco.net/J.deBoynePollard/FGA/fga-not-faq.html at least we can start to post "Have you read FAQ #x?" jaclaz

Some cables NEED a telephone connected to it in order to work. Actually the NEED is for power that is drawn from the telephone battery. (if you check a number of Nokia tweaking guides, you will see that the pre-requisite is that of having a fully charged battery in the phone) The serial number may mean that it is original or that it is a well done "fake". In other words the TTL converter needs to be powered somehow. Some cables draw the power from the +5v/0v from the USB side. Some cables draw the power from the +÷3v/0v from the telephone side. Until the TTL converter is not powered, the device is not detected in Windows. Read these: http://www.msfn.org/board/index.php?showtopic=128807&st=1805 http://www.msfn.org/board/index.php?showtopic=128807&st=1827 jaclaz

@Queue Isn't it the same thing as this?: http://users.cybercity.dk/~bse26236/batutil/help/how/VARIOUS.HTM#jerry jaclaz

Typing the following very, very slowly : READ the post just above yours, in there are the links to the threads you need to read. Just in case: jaclaz

Sure it will, as a USB-TTL is the APPROPRIATE tool, the CA-42 is a SUBSTITUTE tool and due to the number of good and bad cables around it looks like it is a 33% to 50 % probability of getting a "working" one. To recap once again: get an appropriate converter, this thread is choking full of examples to build one AND links to pre-made ones. DO NOT go for a CA-42 cable, unless you ALREADY have a CA-42 cable lying around, in which case ONLY it is worth a shot , chances are that you will : lose some money lose some time post on this tread the nth time whining about a CA-42 NOT working (which, as said is very, very, VERY common). If you are interested on the reasons WHY these ca-42 cables may (or more probably may completely FAIL to) work, read about what they are used for (M-bus/F-BUS, etc.): http://www.panuworld.net/nuukiaworld/hardware/cables/index.htm In a nutshell, and in VERY simplified terms , NOKIA phones use a "protocol" that is a "subset" of the one we need in order to "talk" to the HD. It should NOT be a surprise that some cables can use the "whole" and some can only use the "subset" (which work on Nokia phones but not on the HD). The above is EXPECIALLY valid for people that have problems/difficulties/are not familiar with finding out the appropriate connections/wires, USB-TTL or RS232-TTL converters have MARKED input and output pins/connectors. jaclaz

Just in case: VARSET: http://home.mnet-online.de/horst.muc/div.htm should do the trick. jaclaz

Well, miracles are outside the reach of most of us, or at least outside mine. As said: In other words we do have a program that may be able to add USB boot support to your PC (PLoP), but you have to find a way, ANY way to load and run it, you need "something" that is bootable on that machine, that can be a floppy or a CD, or another hard disk (previously prepared on another machine). jaclaz

I don't understand. Is that ide-USB reader a bootable device or not? List the devices you have connected (or connectable) to that machine: Hard disk drive Floppy disk drive CD or DVD disk drive PLoP can boot from all 3 of them, of course if you ONLY have an internal hard disk there is NO way you can get PLoP on it unless you take it out and copy PLoP to it while it is connected temporarily to another running machine. The Siginet's app is a "wrap around" the actual PLoP bootmanager: http://www.plop.at/en/bootmanager.html That can run BOTH as "hdinstall": http://www.plop.at/en/bootmanager.html#installhd or "no install": http://www.plop.at/en/bootmanager.html#noinstall But SOMEHOW you need to have it on that machine. jaclaz

Hmmm, maybe you need to use an intermediate DIR command, but then you will need a temporary file. http://www.ericphelps.com/batch/lists/filelist.htm What about trying the 9x enhanced command processor? http://www.boot-land.net/forums/?showtopic=2392 It may be possible to avoid the temporary file. I haven't a 9x machine/VM handy to further help you, but maybe this helps (haven't tested it, nor even understood it): http://users.cybercity.dk/~bse26236/batutil/help/how/VARIOUS.HTM (search for LFNFOR on the page) I'll see if I can find some of the good ol' LFN utilities, there may be one capable of doing this "conversion". jaclaz

Here: http://www.msfn.org/board/index.php?showtopic=85842 Just for the record, something that may be of use is the Offline SysPrep: http://www.911cd.net/forums//index.php?showforum=43 which includes a Mass Storage DriverInjector: http://www.911cd.net/forums//index.php?showtopic=22523 jaclaz

Maybe you can use the BAT to find the actual long file name by using one of the most "obscure" commands ever included in 9x: LFNFOR: http://www.nukesoft.co.uk/msdos/command.php?id=60 http://www.robvanderwoude.com/w95lfnfor.php jaclaz

How is the partition table organized? The original IBM partitiontable is not usable, is it? Is there another way to define a partition on an internal (boot) harddisk? Why not? The 24 is given by the 26 letters of the alphabet - A - B (reserved for floppies). You can have 24 partitions allright normally: 3 Primaries 21 Volumes inside Extended jaclaz

I guess it's pointless (as much as these HD fails are unfortunate). I tried to convey this same message n times, but it simply does not "pass-through". http://www.msfn.org/board/index.php?showtopic=128807&st=2690 http://www.msfn.org/board/index.php?showtopic=128807&st=2535 http://www.msfn.org/board/index.php?showtopic=128807&st=1770 I do understand (and sympathize with ) people having problems with their hard disks and that are looking for a solution, but, once again, this is NOT the miracle cure for ANY disease of ANY hard disk. The fact that switching boards is PERFECTLY unuseful on modern hard disks (unless special procedures with special Commercial software and/or hardware changes are performed) and it WON'T solve ANY problem, BUT may create more AND ruin also the "donor" drive, has also been written tens of times in this thread, and what you get? With all due respect to joejetson2 , I do read it very like: Just in case: DO NOT TRY SWITCHING HD PCB BOARDS, EVER! (unless you are explicitly told to do so by someone who knows where his/her towel is AND the FULL procedure is explained AND you have completely understood it AND you have available the needed software AND hardware tools) jaclaz

There are quite a number of virii that do something like that: http://www.runscanner.net/lib/services.exe.html AFTER a thorough antivirus scan, if the behaviour continues, check this: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/edd479ff-6ae3-4255-9add-57acd434c5ac jaclaz

From here: http://www.boot-land.net/forums/index.php?showtopic=9401 you should be able to get a reference for the dependencies. What happens if you just open a command prompt and run in it: WMIC Which exact error are you getting? On a normal build the first time WMIC is run it "installs itself" Is the WINMGMT service started (or can it be started)? jaclaz

Just for the record, following screen should be in SMSS.EXE: http://www.msfn.org/board/index.php?showtopic=113048 jaclaz

Just for the record it should be the issue for which a KB exists but targeted for 2K: http://support.microsoft.com/kb/235032/en-us jaclaz

Yep, it seems like it. Boot-land has been a lot "hectic" to say the least lately. Google cache (text only) temporarily: http://webcache.googleusercontent.com/search?q=cache:Ru7xljO9DSEJ:www.boot-land.net/forums/index.php%3Fshowtopic%3D8944+http://www.boot-land.net/forums/index.php%3Fshowtopic%3D8944 main thread with reports of working iso's is not cached seemingly. jaclaz

You are wrong. (hey, you asked for it!) DOS based .iso files can normally be chainloaded by grub4dos allright. In the case of this particular image, which I personally doubt is actually a "legal copy" of anything, as well as ANY floppy-emulation based image ONLY, it is prefectly pointless, as it is much more convenient to chainload the actual floppy image (as opposed to the container that contains it, i.e. the .iso file). More details here: (reasons why you can't say "any" or "normal") http://www.boot-land.net/forums/index.php?showtopic=8944 JFYI, you may be surprised by the number of .iso's for which there is already a solution : http://www.boot-land.net/forums/index.php?showtopic=5041 jaclaz

You posted here: MSFN Forums > Unattended Windows Discussion & Support > Multi-Boot CD/DVDs Maybe looking here: MSFN Forums > Member Contributed Projects > Install Windows from USB might help : http://www.msfn.org/board/install-windows-f157.html Check the stickies, and particularly these two: http://www.msfn.org/board/index.php?showtopic=120444 http://www.msfn.org/board/index.php?showtopic=121446 jaclaz

36 files seems to me more like a success (almost ) than a failure. If you are lucky it's a matter of a couple small changes. Posting the list of the 36 files that create the problem might help. As well as a link to the thread on HFSLIP Forum where you are trying to find a solution. jaclaz

As expected . WAREZ. http://www.msfn.org/board/index.php?showtopic=18408 jaclaz