jaclaz

Well, no offence whatsoever intended , but you look like the only peep on MSFN - particularly in the "restricted" group of 9x runners- that never heard about ReactOS! It originally started as a re-write from scratch of win 9x and only later "shifted" to NT .... A thread you might be interested in: page__st__121 page__st__128 jaclaz

A number of motherboards have connectors that are two rows (and then are thickier), like this: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3949897&CatId=511 http://www.tigerdirect.com/include/AddCartfromGallery.asp?EdpNo=3949897&csid=ITD&Sku=ULT40299&imgcart=1&imgcounter=3 The difference is easier to understand comparing this: http://www.amazon.com/2-Port-Rear-Panel-Bracket-Adapter/dp/B002IWEDSS/ref=sr_1_3?s=electronics&ie=UTF8&qid=1295689565&sr=1-3 to this: http://www.amazon.com/SIIG-CB-BR0311-S1-2-PORT-USB-Bracket/dp/B001H3DPMO/ref=sr_1_8?s=electronics&ie=UTF8&qid=1295689565&sr=1-8 The "correct" name is "dual headers": http://cgi.ebay.it/4-Port-USB-2-0-Expansion-Bracket-to-Dual-USB-Headers-/370472863354 Single: http://frontx.com/con_guide.html Dual: http://frontx.com/cpx108_2.html Four ports to 4 single headers are quite rare. You can still modify them if you happen to have a few standard 0.1"/2.54 mm pitch in-line 4 or 5 pins connectors (typically from an old case you can find in *any* junkyard but also from unused CD "audio" connection cables, if I recall correctly they are "plain" Molex 70066-G ) http://frontx.com/head_con.html jaclaz

The "normal" way a hard disk with a recovery partition is set is the following: hidden partition with recovery settings/files visible partition with OS and all programs running (the order in which they are is not important) In normal operation: BIOS->MBR->PBR of active partition->Normal OS booting In Recovery operation: BIOS->MBR->HotKey pressed->Recovery partition is unhidden and set Active->PBR of active partition (which is now the recovery partition)->Recovery OS booting What happens with the "new" approach should be something like: In normal operation: BIOS->MBR->PBR of active partition->BOOTMGR->BCD->Normal OS booting In Recovery operation: BIOS->MBR->BOOTMGR->BCD->HotKey pressed->Recovery OS booting (WINRE) ->get data from factory.wim->restore OS Compare also with this (Dell specific - but actually "general"): http://www.goodells.net/dellrestore/vista/vistarecovery.htm From what I can see there, the partition holding the Factory wim is not hidden on Dell's. It is possible that your particular PC has a "mixed mode", where the Recovery partition where the Factory.wim is, is hidden and unhidden when booting the WinRE. If you follow the setupfailover.cmd, you will find: REM REM Hide partition REM if not {%NOHIDE%}=={} ( goto :EOF ) set TEMP_FILENAME=%SCRIPTNAME%_Temp_DiskPart.txt echo sel disk %DISK% > %TEMP_FILENAME% echo sel partition %PARTITION% >> %TEMP_FILENAME% REM REM Remove the drive letter for the partition before hiding it. REM The system will not allow us to remove the drive letter after hiding it. In other words, when the original setupfailover.cmd is run, the hidden partition is unhidden and has a drive letter assigned to it (which should be the parameter you were asking about) then the batch itself removes the drive letter and hides the partition. Hope that now it is more clear... jaclaz

Good. One more happy bunny: but in Brooklyn : http://www.bklynbunny.com/ jaclaz

Loopback has NOTHING to do with Grounding. If you do not understand the read-me-first, ask for help to a more knowledgeable (local) friend possibly not the same that seemingly fried your converter... How do you expect that we can now what the heck has happened to your converter from a distance? It may well have been fried or it could be a "cold" soldering or a broken LED. jaclaz

There are TWO kind of "headers". Most are actual USB headers, and all you need is a cable. Some are actually need some active components (please read as "daughterboard"). If you have the first kind, you simply buy cables similar to these: http://frontx.com/panel_mount.html http://www.frontx.com/cpx101_2.html http://www.performance-pcs.com/catalog/index.php?main_page=product_info&cPath=34_81_250&products_id=1550 http://www.performance-pcs.com/catalog/index.php?main_page=product_info&cPath=34_81_250_150&products_id=269 http://www.performance-pcs.com/catalog/index.php?main_page=product_info&cPath=34_81_250_150&products_id=567 http://cgi.ebay.it/ASUS-Motherboard-USB-Connectors-2-0-Internal-Cable-/230514927731 If you have the second kind, usually you can buy a new motherboard for the price of a stoopid daughterboard from the manufacturer. jaclaz

Let me doubt about it. Yes, that's the idea. As CLEARLY stated there. (Point #8 of the read-me-first.). jaclaz

WHICH directions? THESE ones, the ones recommended in read-me-first, that you most probably have NOT read : http://www.mapleleafmountain.com/seagatebrick.html (the second you said) READ the readme first. DO a loopback test BEFORE anything else. jaclaz

I will try to rephrase my previous post. We have reports that: UNTOUCHED original SP2 sources do work with WinSetupFromUSBwithGUI UNTOUCHED original SP3 sources do work with WinSetupFromUSBwithGUI Then we have reports that : UNTOUCHED original SP2 sources with SP3 ONLY integrated do work with WinSetupFromUSBwithGUI Then we have few reports that: MODIFIED original SP2 sources with SP3 integrated DO NOT work with WinSetupFromUSBwithGUI MODIFIED original SP3 sources DO NOT work with WinSetupFromUSBwithGUI Please consider that a MODIFIED original SP2 sources with SP3 integrated may work on CD and fail on USB stick. As well it is possible that something ELSE is causing the problem (the steps you take when using WinSetupFromUSBwithGUI, the hardware you are testing on, whatever) A very good way to understand if it's the latter or the former is to have a report of what happens when you try using the same steps on the same hardware BUT using an UNTOUCHED source, known to be working for all the other people using the program. jaclaz

And... ...have you tried the modified NTDETECT.COM? ....WHICH STOP ERROR are you getting ?(if NOT a 0x0000007b - BTW I was SURE that my crystall ball was actually perfectly tuned ) I'll try again: you DESCRIBE what happens with ALL main, EXACT details and possibly someone can help you. ESP capabilities are not common on technical boards... Last attempt . jaclaz

No prob , anyway I had LIED to you. On some machines you may need to modify the 2K/XP MBR nonetheless : http://reboot.pro/2246/ http://reboot.pro/2246/page__st__15 Or you can use the upatch command in MBRBATCH.CMD: http://reboot.pro/3191/ http://reboot.pro/3191/page__st__42 http://reboot.pro/3191/page__st__49 jaclaz

Newbies should usually READ FAQ'S, now WHY there would be a thread titled: FAQs Please read before starting a new topic You might be interested in FAQ #3. Next time you ask for help, don't go around talking about "a blue screen", what you are having is a VERY SPECIFIC BSOD (Blue screen of death) with STOP ERROR 0x0000007b don't expect that other people have their crystall balls handy (ot that they have them properly tuned ). This represents an useful reference : http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html jaclaz

Which means "NO reports"? jaclaz

Only if disk/partition size is 2GB or less. FAT 16 can be "extended to 4 GB and FAT doesn't mean "FAT16" inly, it may ALSO mean "FAT32". :whistling: Just for the record (anf for the interest of donpham) there may be trade-offs : jaclaz

Sure , you can dial the hard disk phone number and wait until it lifts the (small) headset on it's side.... ... come on ..... .... unless you have a "special edition" modem that outputs TTL and actually low-level TTL ONLY, of course AFAICR, they stopped making those internal modems before 2003 .... The second you said. Guess why "internal modem (on a 2003 powerbook)" is NOT listed in the read-me-first: and NOT even in the FGA's: It is evident that I was wrong at the time: We need to add to FGA's a list of the most crazy things people can think can be used to connect to the stoopid HD instead of the proper converters/data cables (and that won't work). Right now we have, in no apparent order : a car battery a direct connection to mains a serial port scanner my cousin Vinny trashed in 1992 because it was broken an internal modem (on a 2003 powerbook) an i-pod charger the audio output of a Marantz amplifier connected to a Pioneer record player, playing an early 1959 original recording of "Love me do" a morse If it WAS NOT clear: NO , you need a specific type of converter of data cable, whose specifications have been written a few hundred times by now, as well as a number of example of *ANYTHING* that can output (and input) TLL levels (low voltage type) and that can be somehow connected to hyperterminal SUCH DEVICES will do, and NOTHING ELSE will (but you can also build one from scratch parts - but you want to build a RS232/TTL converter and NOT a modem). ...and NO, not even a good ol' J38 key: wil work. And now, for NO apparent reason, a LOLCAT LOLMOUSE: jaclaz

Similar SXS.DLL "ASMS" related errors are traditionally (from CD) a sign of: a non-original (or however "messed with") source a bad burn (or an .iso created with "wrong" mkisofs parameters) I wonder what can be the problem on a USB stick. If I were you I would try with a "clean" SP3 (without your mods/integration/unattended/whatever) first, and then with the SP2 "original", should have the slipstreaming of SP3 has caused the problem, BTW HOW was it slistremed? (directly, using. nlite, any other program) jaclaz

Or maybe a legitimate MS support technician dialed the wrong number? jaclaz

@Cosmin3 How to use the utility was in the given link, but on second thought I might have sent you on a wild goose chase , the 500 Gb is NTFS or FAT32? If the latter findpart chsdir would be useful, if NTFS won't. You can use DMDE: http://softdm.com/ which is also much easier to use , you simply open the volume and open the grldr file in it, at the top of lower window you will see something like: phys sec: 130915591 [CHS:8149:30:17] vol.sec:130915528 Clus:16364441 sec: 0 Mind you the following is just my personal opinion: I personally never liked the idea of installing the grub4dos grldr.mbr to MBR (+hidden sectors) because it is non-standard. (and because I happen to often have to deal with "strange" software that happen to write or read from hidden sectors). I normally use the "standard" Windows 2K/XP MBR and then load grldr from an entry in BOOT.INI or I edit the "standard" 2K/XP PBR to invoke GRLDR instead of NTLDR. The general idea is that no-matter how demented the BIOS programmers may have been , there are greater probabilities IMHO that they tested at least their code against a "standard" MBR and PBR of one of the most common OS which code has not changed in 10 years. There is an ongoing project for a "minimal" grub4dos MBR code which you may also want to follow: http://reboot.pro/12436/ jaclaz

Let's start disambiguating. There exist NTFS filesystem drivers for DOS and for Windows 9x/Me. These will allow ACCESS (READ) to files residing on a NTFS formatted partition - some may allow also WRITING to the NTFS filesystem. BUT - depending on the SIZE of this partition oand/or of the disk - more patches/fixes/whatever may be needed. A program that can run under Windows 9x/Me may start and run if accessed with such a driver, BUT there are tens of factors that may influence it running succesfully, like dependencies, paths, direct access to hardware, etc., etc.. As such there is not a definite answer for " Is it possible to execute a program in a NTFS partition from windows 98 SE ?". Drivers are listed here: This board does have a search function, you know, like searching for "NTFS" in: MSFN > Microsoft Software Products > Windows 95/98/98SE/ME you may have found the above referenced thread and threads like (examples): You may have found same or other related links/info. jaclaz

JFYI : http://www.911cd.net/forums//index.php?showtopic=24245&hl= jaclaz

Start a new thread - as to NOT further clutter this one, and I'll see what I can do. Still, it's a CATCH22 situation : whoever can do a PCB swap won't ask about it if you ask about it you CANNOT perform a PCB swap jaclaz

NO. This is ONLY for 7200.11 Seagate drives! READ the read-me-first: Is there something difficult in the above? Start a NEW thread - aptly titled - for your problem which is COMPLETETELY UNrelated to Seagate 7200.11, here: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/ jaclaz

Naaah , there is NO secret ingredient. http://www.imdb.com/title/tt0441773/quotes?qt0448742 jaclaz

ADDITIONAL to what cdob advised (possible problem of the BIOS with drives with single partition going over the 28 bit LBA barrier), can you check the actual position of grldr (and .lst files) in the partition? A suitable tool is FINDPART: http://www.partitionsupport.com/utilities.htm A quick example of it's usage: http://reboot.pro/1647/ Maybe a red herring, but it is also possible that the problem is due to the location of key files in relatively "high address" areas of the disk. jaclaz

Sure, I did , and I do take the full responsability of subtracting your "about 5%" from 100% (perfection) and compute the range 95%÷100% If it's a single computer, than I wonder how you got the mentioned "about 5%", meaning as: 1/20=5% or 10/200=5% or 49/1000=4.90% or "about 5%" (just trying to establish a range for the "many" computer you tested) I just renamed the thread from: to: I hope this will be agreed upon, so that we can workaround the semantics and move forward .... jaclaz