jaclaz

Check this : http://ccollomb.free.fr/unlocker/ jaclaz

Then, please comment on these too : http://www.microsoft.com/windows/internet-...ts/default.aspx http://www.microsoft.com/windows/internet-...comparison.aspx http://www.microsoft.com/windows/internet-...ythbusting.aspx I'll make an exception to my current no-comment stance to say that the "get-the-facts", though a nice marketing motto , is the single most misleading name for a web subdirectory I have seen in my life. jaclaz

Windows and PE 1.x WON'T work unless you use a RAMDISK approach (from .iso) PE 1.x will work with "usual" "\I386" structure, Windows install will work as well from "\I386", so i fyou have both you will need to rename one of the two and hexedit correspondingly files, there is no way if not "Hard disk emulation" to run "Full XP" from CD-ROM (not usable in a mult-boot, AFAIK): http://www.boot-land.net/forums/?showtopic=3890 For all the rest you may want to search around, and test the newish Syslinux ISO mapping features. Start from grub4dos: http://www.boot-land.net/forums/index.php?showforum=66 and see if what works with it: http://www.boot-land.net/forums/index.php?showtopic=5041 also works with Syslinux: http://www.boot-land.net/forums/index.php?showtopic=8258 in any case in the forum there are grub4dos examples and "translations" from grub4dos to Syslinux syntax, so that you can use them the other way round. jaclaz

I'll just throw this one on the table, without comments : http://www.qtweb.net/qtweb.php http://www.qtweb.net/compare.php http://www.qtweb.net/download.php jaclaz

AFAIK, the motor should NOT be disconnected (otherwise what's going to spin down? ). Read here: http://www.msfn.org/board/index.php?showto...8807&st=464 jaclaz

Unless jetman's crystal ball (unlike mine ) works very, very well, I wonder how he could, in 2007, have foreseen that on May 12th, 2009 : http://www.sysresccd.org/news/2009/05/12/s...d-120-released/ a new version would have been released, that it would have been a "major release" and that probably the booting files have been changed names.... From here: http://www.sysresccd.org/Sysresccd-manual-...your_own_kernel it seems like the new files are vmlinuz and initram.gz label mykernel kernel vmlinuz append initrd=initram.igz label mykernelfr kernel vmlinuz append initrd=initram.igz setkmap=fr The files in NTPASSWD, I guess are related to NTPASSWD aka chntpw aka Offline NT Password Editor : http://home.eunet.no/pnordahl/ntpasswd/ jaclaz

Yes, it is too low on the RX and TX lines, but it depends greatly on how you measure it. http://en.wikipedia.org/wiki/Transistor...ransistor_logic jaclaz

Did you wait a few seconds and then issue a CTRL Z ? : http://www.mapleleafmountain.com/seagatebrick.html jaclaz

isn't it where it should be? I.e. in this file: http://www.kernel.org/pub/linux/utils/boot...slinux-3.82.zip in the "memdisk" directory, as a file 19.584 bytes in size, called "memdisk" (with no extension) jaclaz

I am not offended at all. What I was trying to convey is that I know next to nothing about driver integration, that Fernando1: http://www.msfn.org/board/index.php?showuser=58937 knows a lot about the topic, and that it is unlikely that he will notice this thread/your request for help, and thus it is not probable he might help you. I presume that posting in there a request for help pointing to this thread may be the "right" thing to do. jaclaz

Right now grub4dos and syslinux are pretty much "exchangeable", newish versions of syslinux have the ability to use "chain.c32 that allows booting windows too. If you search for "syslinux" in the grub4dos forum you will find many "translations" from Sysllinux to grub4dos syntax, that you can use as a reference the other way round. jaclaz

...or a good ol' plain DOS 7.x/8 diskette (read win9x/Me), with EDIT.COM (for FAT16 and FAT32 volumes) and this app Freeware from Terabyte Unlimited (for NTFS ones): http://www.terabyteunlimited.com/downloads-free-software.htm EditBINI http://www.terabyteunlimited.com/downloads/editbini.zip or ftp://terabyteunlimited.com/editbini.zip Or you add to the stick a floppy image created along these lines: http://www.xxcopy.com/xxcopy33.htm With a "wide minded" BOOT.INI, something like this one: http://www.msfn.org/board/index.php?showtopic=25365 Some hints are given here: http://www.msfn.org/board/index.php?showtopic=127900 jaclaz

Hmm, I thought it was a re-install, not a "brand-new" one. OK, I would say time to go with plan "B" (don't worry, we do have plan "C", "D", and probably a few more): Time to risk a bit (again don't worry, unless you do something weird, there won't be problems): Plan "C", should you not want to go for plan "B" above: Can you please attach a copy of your current MBR of the stick - the one which is booting now - (it should be one of the files I sent you, buit I've lost track whether we did some mods to it)? I can try adding a second "fake" partition to it and see if the findings of member Online on boot-land apply to your Asus, or you could try doing it directly: Access the stick (Physicaldrive n) with beeblebrox: http://students.cs.byu.edu/~codyb/ You should see a single entry "filled" with these data: #0/0E/80/0/1/1/490/254/63/63/7.887.852 and the other three ones "blank". now, add this data to second entry: #1/21/00/491/0/1/491/0/63/7.887.915/63 This post has a screenshot that could help in guiding you doing the above: http://www.boot-land.net/forums/index.php?...=7739&st=54 jaclaz

Sure : Hmmm, try putting a copy of menu.lst on your internal hard disk, in C:\menu.lst. grldr ahould be able to find it. Once you are in it, press "c" for command line, and try issuing the commands previously listed. Sure , that's the normal "safe mode" of Windows. jaclaz

@lawson23 Just for the record, jaclaz DID NOT post ANY instructions. He posted a link to a specific thread on this board giving the instructions AND specifically troubleshooting issues deriving from them. Wouldn't it appear "logic" to post on the referenced thread: http://www.msfn.org/board/Integration-of-I...ve-t107504.html a report and request for help/troubleshoot? Maybe the Author of the method knows a bit more about his creation than a guy simply pointing to it... and there are possibly more probabilities he would notice the issue on "his" thread than on this one. jaclaz

We are talking two different languages. Did you use Notepad (which is NOT a hex-editor) to change the menu.lst file or the embedded menu.lst INSIDE grldr? However, it doesn't matter, simply try this:

There is not one reason in the world to slipstream SP3 (which can mean trouble on OEM) for a "once upon a time" installation, if not that after you later upgrade the installed system to SP3, the original (SP2) disk won't be able to do a Repair install. It's up to you the choice. Usually OEM keys don't go well with non-OEM source. SONY's have usually a Recovery Partiiton and/or a "local" source, from which you may want to use to re-create a "full" install CD or just get the drivers. Here is some reference: http://www.msfn.org/board/Cannot-access-CD...P-i-t91907.html The method is right, I personally try to use only Freeware tools, like: SIW: http://www.gtopala.com/ or SIV: http://rh-software.com/ jaclaz

It's low for proper working. That board IC "likes" a minimum of +3 V, and has NO problems up to 5.5V: http://www.maxim-ic.com/quick_view2.cfm/qv_pk/1069 Use 3 AAA or AA batteries=÷4.5V if "normal" or =÷3.6V if "rechargeable" (if you are afraid of connecting a "full" +5V from a motherboard or if you incur in "grounding" problems) jaclaz

It seems to me like a fairly "standard" "autogenerated" reply, this summed with the following: makes me think that it is a "glitch in the matrix", i.e. the auto-responding/auto-e-mailing system that sent you the wrong kind of letter. (maybe it was programmed by the same guy that programmed the software leading to the 320, and that was demoted to Customer Assistance ) If I were you I would write them asking (politely ) how the heck they managed to hear the clicking sound since the drive is actually still in the hands of UPS. Or they directly outsourced the engineering department to UPS? Or possibly UPS not only has a fairly messed up tracking systems , but also one of the delivery guys dropped your hard disk to ground..... jaclaz

Checking the "mbrfix" version. Something is simply NOT right. Preliminary: the "EXIT" in the first few lines is not a good idea (for people that run the batch from Command Prompt) first part of the output: All drive letters: C D M N O P Q R Y Mounted drive letters: C D M N O P Q R Virtual drive letters: Y Internal hard disk 1 drive letter: C Internal hard disk 2 drive letter: D Internal hard disk 3 drive letter: {80cf88c6-8a34-11dd-813c-806d6172696f}R {80c f88c6-8a34-11dd-813c-806d6172696f}R {80cf88c6-8a34-11dd-813c-806d6172696f}R {80c f88c6-8a34-11dd-813c-806d6172696f}R {80cf88c6-8a34-11dd-813c-806d6172696f}R {80c f88c6-8a34-11dd-813c-806d6172696f}R {80cf88c6-8a34-11dd-813c-806d6172696f}R {80c f88c6-8a34-11dd-813c-806d6172696f}R {80cf88c6-8a34-11dd-813c-806d6172696f}R Cd/dvd rom drive letters: M Removalbe drive letters: N O P Q R A minor typo:Removalbe->Removable the call to :vdrv creates havoc, as the %1 is "{80f886-8a34-11dd-813-806d6172696f}R" Mounted drive letters is NOT sorted and probably cause something queer, or some variable are left after batch competion, on second run: All drive letters: C D E F G H I J Y Mounted drive letters: C E D F G H I J Virtual drive letters: Y Internal hard disk 1 drive letter: C Internal hard disk 2 drive letter: E Internal hard disk 3 drive letter: {80cf88c6-8a34-11dd-813c-806d6172696f}J {80c f88c6-8a34-11dd-813c-806d6172696f}J {80cf88c6-8a34-11dd-813c-806d6172696f}J {80c f88c6-8a34-11dd-813c-806d6172696f}J {80cf88c6-8a34-11dd-813c-806d6172696f}J {80c f88c6-8a34-11dd-813c-806d6172696f}J {80cf88c6-8a34-11dd-813c-806d6172696f}J {80c f88c6-8a34-11dd-813c-806d6172696f}J {80cf88c6-8a34-11dd-813c-806d6172696f}J Cd/dvd rom drive letters: D Removalbe drive letters: F G H I J In :vdrv: :vdrv set nk=!fulldrv:~%k%,1! if /i %1 neq !nk! ( set ordereddrv=!ordereddrv! %1¡ú!nk! mountvol %1: /d set viddrv=!viddrv! !totalvid:~%e%,38!!nk! ) goto :eof there is something strange, what the heck is ¡ú maybe some "extended characters" of some kind? The batch continues with a bunch of errors, too many to pinpoint at the moment, then I get this: ORDERED DRIVE LETTERS: {80f886-8a34-11dd-813-806d6172696f}Jí·D {80f886-8a34-11d d-813-806d6172696f}Jí·E {80f886-8a34-11dd-813-806d6172696f}Jí·F {80f886-8a34-11d d-813-806d6172696f}Jí·G {80f886-8a34-11dd-813-806d6172696f}Jí·H {80f886-8a34-11d d-813-806d6172696f}Jí·I {80f886-8a34-11dd-813-806d6172696f}Jí·J {80f886-8a34-11d d-813-806d6172696f}Jí·K {80f886-8a34-11dd-813-806d6172696f}Jí·L Eí·M Dí·N Fí·O G í·P Hí·Q Ií·R Jí·S and later on this: Internal hard disk 3 drive letter: Usb hard disk 1 drive letters: C Usb hard disk 2 drive letters: D Cd/dvd rom drive letters: M Removalbe drive letters: N O P Q R and later on this: ORDERED DRIVE LETTERS: Mí·D Dí·E Ní·F Oí·G Pí·H Qí·I Rí·J The diskpart version behaves a bit better, but still NOT WORKING (as well with the EXIT REMmed out): first run: C:\Downloaded\md5\diskpart>orderdrv_diskpart "orderdrv_diskpart.cmd" non è riconosciuto come comando interno o esterno, un programma eseguibile o un file batch. All drive letters: C D E F G H I J Y Mounted drive letters: C E D F G H I J Virtual drive letters: Y Internal hard disk 1 drive letter: C Internal hard disk 2 drive letter: E Internal hard disk 3 drive letter: Cd/dvd rom drive letters: D Removalbe drive letters: F G H I J ORDERED DRIVE LETTERS: Eí·D Dí·E Premere un tasto per continuare . . . !nk! non atteso. Second run: Again a small typo: DIRVE LETER ORDER IS CORRECT ->DRIVE LETTER ORDER IS CORRECT As a reference this is the "right" set of mounted drives on the same machine (using ddlistw.cmd): C:\VSS>ddlistw3 Drives by drive letter: c: 0,1 FIX \Volume{b0b284c3-8a33-11dd-8781-806d6172696f} \HarddiskVolume1 d: 1,1 FIX \Volume{b0b284c4-8a33-11dd-8781-806d6172696f} \HarddiskVolume2 e: x,x CDR \Volume{80cf88c2-8a34-11dd-813c-806d6172696f} \CdRom0 f: 2,1 REM \Volume{5d3e8800-9c1f-11dd-8148-001fc6bb76ce} \Harddisk2\DP(1)0-0+5 g: 3,1 REM \Volume{80cf88c3-8a34-11dd-813c-806d6172696f} \Harddisk3\DP(1)0-0+a h: 4,1 REM \Volume{80cf88c4-8a34-11dd-813c-806d6172696f} \Harddisk4\DP(1)0-0+b i: 5,1 REM \Volume{80cf88c5-8a34-11dd-813c-806d6172696f} \Harddisk5\DP(1)0-0+c j: 6,1 REM \Volume{80cf88c6-8a34-11dd-813c-806d6172696f} \Harddisk6\DP(1)0-0+d Premere un tasto per continuare . . . Drives by connection: c: 0,1 FIX \Volume{b0b284c3-8a33-11dd-8781-806d6172696f} \HarddiskVolume1 d: 1,1 FIX \Volume{b0b284c4-8a33-11dd-8781-806d6172696f} \HarddiskVolume2 f: 2,1 REM \Volume{5d3e8800-9c1f-11dd-8148-001fc6bb76ce} \Harddisk2\DP(1)0-0+5 g: 3,1 REM \Volume{80cf88c3-8a34-11dd-813c-806d6172696f} \Harddisk3\DP(1)0-0+a h: 4,1 REM \Volume{80cf88c4-8a34-11dd-813c-806d6172696f} \Harddisk4\DP(1)0-0+b i: 5,1 REM \Volume{80cf88c5-8a34-11dd-813c-806d6172696f} \Harddisk5\DP(1)0-0+c j: 6,1 REM \Volume{80cf88c6-8a34-11dd-813c-806d6172696f} \Harddisk6\DP(1)0-0+d e: x,x CDR \Volume{80cf88c2-8a34-11dd-813c-806d6172696f} \CdRom0 jaclaz

Just for the record, there is a "simplified" driver for USB (instead of the however very good NUSB), that in my experience worked nicely and almost "out of the box" on non-English systems: http://www.msfn.org/board/index.php?showtopic=99220 jaclaz

@livetek The thread you referenced CLEARLY says: that Quake 3 requires DX9 installed that it is possible under Vista to install DX9 alongside with DX10 (and possibly DX11) Have you tried installing DX9 on your Windows 7? If not, that's the first thing I would try if I were you. Download is here: http://www.microsoft.com/downloads/details...;displaylang=en Windows 7 "should" have a technology "10level9" to avoid this kind of problems, but maybe it is not working yet: http://windows7news.com/2008/11/26/windows...ect3d-10level9/ jaclaz

Then, add the line: multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="USB Repair" /noexecute=optin /fastdetect to the BOOT.INI of BOTH your 20 Gb and 80 Gb HD. Something is not "kosher" on the BOOT.INI you posted, however: The contents of the Default line should correspond to one of the choices under [Operating Systems]. jaclaz

The answer is 320 NO, with the new firmware it shouldn't happen anymore. See here (posts from 1034 to 1049 : http://www.msfn.org/board/index.php?showto...092&st=1033 and this one: http://www.msfn.org/board/index.php?showto...092&st=1061 (for a pretty much unuseful , but nice graphic ) jaclaz

There is a way, though cannot say if it will be of your liking. It involves the use of a special (was Commercial) driver, of which I have a copy of the Demo, which will work allright, but will reboot in 20 minutes (if I recall correctly). The old page was here: http://www.msfn.org/board/index.php?showtopic=35703&st=3 Via Wayback Machine: http://web.archive.org/web/20060714185751/...roducts/AB.php3 Maybe it is possible to use anyway some of the newish findings and "backport" something like ETBOOT: http://www.boot-land.net/forums/index.php?showtopic=3890 or Diskless Angel (free version limited to 640 Mb) or even the 2003 SP1 Ramdisk. @BogdanV I'll see if I can find the copies of the "stripped down" Registry, that you may use as a quick reference. jaclaz