jaclaz

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

NO prob. Let us know how it goes. jaclaz

Full disclosure about "lacking of disclosure", if I get it right. jaclaz

You don't want a video (which is a good thing, but NOT for these kind of things, where a missing comma may be a BIG problem) You want a clear, illustrated, step by step tutorial which you can print, read, re-read and understand before trying... ...which you can find here: http://www.msfn.org/board/index.php?showtopic=133387&hl= http://www.mapleleafmountain.com/seagatebrick.html jaclaz

I don't think nlite was ever mentioned until you did. jaclaz

If we are going to start debating "value for byte downloaded" The answer (speaking of something pre-install) is IMNSHO UBCD: http://www.ultimatebootcd.com/ which contains, beside parted magic, a great number of diagnostic utilities, everything in a 115 Mb .iso also downloadable as 87 Mb 7-zip SFX. jaclaz

That projects does exactly that, though for XP. I don't think the changes between 2K and XP are that much. If you are interested I do have somewhere (it may take some time to find it) a Win2K SP0 build fitting in 80 Mb with a greatly (though not at the same "essential" level of the referenced XP one) reduced Registry and still using the "full" Winlogon. References here: http://www.msfn.org/board/index.php?showtopic=41208 http://www.boot-land.net/forums/index.php?showtopic=5679 One of the missing steps (largely due to the complete lack of interested members) of the referenced project is the ability to switch form the current "only minlogon" status (which might be one of the reasons of the scarce interest in it) to a "switchable minlogon/winlogon" status, that should enlarge the intended "audience". jaclaz

And you post in MSFN Forums > Unattended Windows Discussion & Support > Multi-Boot CD/DVDs a question about USB UBUNTU? You should read a bit here: http://www.msfn.org/board/index.php?showforum=157 different methods: http://www.msfn.org/board/index.php?showtopic=111406 http://www.msfn.org/board/index.php?showtopic=120444 http://www.msfn.org/board/index.php?showtopic=121446 (Yes, they use grub4dos) (Yes they allow multi-booting with Linux builds) And possibly "mix" with UnetBootin: http://www.boot-land.net/forums/index.php?showforum=79 http://www.boot-land.net/forums/index.php?showtopic=6958 And info in the grub4dos Forum: http://www.boot-land.net/forums/index.php?showforum=66 http://www.boot-land.net/forums/index.php?showtopic=7834 http://www.boot-land.net/forums/index.php?...=5041&st=20 jaclaz

I know that it may make you "deviate" from your original goal , but maybe, just maybe, you can find in this thread something that could be of use: http://www.boot-land.net/forums/index.php?showtopic=3717 In any case, these could give you some hints on how to perrform the integration: http://www.msfn.org/board/index.php?showtopic=72864 http://www.mp3car.com/vbulletin/winnt-base...lite-image.html jaclaz

See if either of these help : http://www.felgall.com/doswin58.htm http://social.msdn.microsoft.com/Forums/en...e2-3c8b50ac550b jaclaz

You are right, my bad. The behaviour of FORMAT changed with Vista, here is the reference article: http://support.microsoft.com/kb/941961/en-us I take back all the previously said, that remains however valid but only "up to" XP or Server 2003. jaclaz

Surely NOT! Please read these threads, where some details are explained: http://www.msfn.org/board/index.php?showtopic=125900 http://www.msfn.org/board/index.php?showtopic=134982 If you do not trust the info above, read the difference between "quick" and "full" from the actual makers of the FORMAT command: http://support.microsoft.com/kb/302686/en-us (they should know what something they've written does ) jaclaz

You may be interested in this: http://www.msfn.org/board/index.php?showto...134982&st=0 With a "normally" working HD, it is not "normally" needed to do a "Full Format". When installing/re-installing from scratch, it is "better" in the sense of "safer" to: wipe the hard disk, possibly with SecureErase: http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml check the disk with it's manufacturer diagnostics utilities (which should update the "firmware" mapping of bad sectors) - sometimes the same utility also has a "wipe" one format it "normally" during setup Using DISKPART, you can easily "script" it, using it's /s option or "feeding" it a script file with redirection: http://www.ss64.com/nt/diskpart.html or using a "self-contained" batch: http://www.msfn.org/board/index.php?showto...26069&st=16 http://www.msfn.org/board/index.php?showto...26069&st=19 jaclaz

Off-topic, but not much , and just FYI (and for a quick laugh): http://www.msfn.org/board/index.php?showtopic=133835 jaclaz

Just for the record, and FYI, there is this thingy, based on a prollish new and experimental OS, Visopsys: http://visopsys.org/ Partition Logic: http://partitionlogic.org.uk/ Of the Linux distro's, the one I personally prefer is Parted Magic: http://partedmagic.com/ ALSO included in UBCD: http://www.ultimatebootcd.com/ jaclaz

Sure , if you run a hardware detecting program and post the exact kind of hardware that PC has, someone may be able to provide you publicly available links to download the software. The currently available technology prevents from actually downloading hardware at the moment. ....something connected to pieces of not properly compressed pieces of silicon jamming into cable bends.... Otherways you will have to wait for these three things to happen concurrently: another user of the board has that exactly same hardware the same user is willing to help you the same user knows where to download the appropriate drivers from ...at an approximate probability level of (120504-2)=120502 to one against. jaclaz

Completely off-topic, but not much an interesting article on the growth of Office suites: http://www.oooninja.com/2008/05/openoffice...ice-moores.html jaclaz