jaclaz

RTFM? After you are satisfied with the Analysis and with the "temporary" partition mapping TESTDISK gives you , you simply write the values to the MBR from within the program and exit (advised is to disconnect and re-connect the device). @wcology Happy there is now another happy bunny, thanks to TESTDISK! jaclaz

Wait a minute... Stop it now.! (if you need to recover data from the "other" partitions). Most probably the partitioning attempt wiped the partition table, you should run TESTDISK in order to try and recover the "missing" partitions. Only once you have backed up the data, start again fiddling with partitioning tools. http://www.cgsecurity.org/wiki/TestDisk AFAIK WintoFlash is intended for use on a Flash device (please read as USB stick), creating a single partition on it: http://www.msfn.org/board/index.php?showtopic=137540 We do have here a whole Forum dedicated on installing Windows from USB with methods that cover BOTH "flash" and HD's: http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Additionally, are you wanting to run an install of XP FROM a USB device? If yes, it is not so easy as you might think. Solutions: http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Why not using a USB midi? jaclaz

Is it a USB external enclosure, is it? Unless all the 1's has gone on one side due to centrifugal force (1's weight more than 0's) it shouldn't happen. Seriously, possibly it is a false impression you had. Unfortunately not much, and definitely nothing with Vista. There are a few DOS programs that may be able to diagnose the problem, but first of all I would try the DOS WD utilities: http://support.wdc.com/product/download.asp?groupid=502&sid=2〈=en but you will need a floppy drive (or burn a bootable CD with the floppy image. jaclaz

Thanks. Found something "in the right direction": http://www.codeproject.com/KB/system/FontEnumerator.aspx but NOT really "it". This is almost it (Excel VBA): http://www.pcreview.co.uk/forums/thread-3794133-1.php http://www.pcreview.co.uk/forums/showpost.php?p=13163743&postcount=7 jaclaz

Yep. Some details (coming from fdv) are explained here by Kiki Burgh: http://www.msfn.org/board/index.php?showtopic=71256 jaclaz

Nice game, can I play too? ?Have you tried Partition Logic? ?Have you tried PartedMagic? jaclaz 2 - submix8c 1 jaclaz

I don't think there is a way out, unfortunately. Which chip does that thingy has? There are Sample drivers for MPU-401: http://msdn.microsoft.com/en-us/library/dd163170.aspx (whatever it is) How is it detected with programs like SIW or SIV: http://www.gtopala.com/ http://rh-software.com/ under Windows XP? I remember having some success with NT 4.0 Sound drivers in XP, but really cannot say for Midi: http://www.drivermuseum.com/files/drivers/sound_d.html jaclaz

Well, I guess they made Disk Signature in the MBR and in the Registry EXACTLY to avoid that. jaclaz

Really? Spyware? jaclaz

No, I don't think it would work. The VM will have it's own Virtual Sound Card. Post some details on the card, it's possible that there are other ways to access it. If you have a FAT32 partition, you can dual boot with 98, or use a "portable" 98 from CD: jaclaz

Oh my, this seems like a circular reference! jaclaz

I don't think that fixing entries similar to this "\Device\HarddiskVolume1\Boot\BCD" can work, mainly because XP does NOT use the BCD. jaclaz

We have a WHOLE Forum for this, with several different methods, here: http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

@Ponch Maybe if you call it WFP instead of SFC, you can find something : Then, you may want to try again searching for SFC : Obviously half the links on them have gone beserk, but if you are interested you can re-build 'em: There were some problems with them not so long ago: And now, thanks to the good IPB developers we have now a whole new syntax for friendly names , totally different from old ones, but you should get the hang of it easily. jaclaz

can you point me, where can I find this collection ? there is an alternative to EXTRACT.EXE with name IMGCPY which may help BeatZero not writing scripts again. I don't get it. The page is here: http://www.frontiernet.net/~fys/mtools.htm First few lines: Link to: http://www.fysnet.net/zips/mtools.zip Inside the zip, a direcftory named IMGCPY, containing: 1) imgcpy.exe 2) imgcpy.c 3) readme.txt Spoon feeding brought to an entire new dimension jaclaz

Well, this is usually called a truism : http://en.wikipedia.org/wiki/Truism jaclaz

If the SATA drive on your LAPTOP is in one of those LAPTOPs that have a removable bay for SATA 2,5" drives, and this is what you refer to when you talk of re-seating the drive, from what you report it is likely that a contact between the bay and the case is not thoroughly clean. A good way to clean them is using an (almost unfindable nowadays) eraser for ink/typewriter (NOT an eraser for pencils): http://en.wikipedia.org/wiki/Typewriter#Correction_methods also, the blue side of things like this: is not bad. Rub gently, only to remove dirt/oxide, contacts are generally *gold* plated, if you insist too much you may remove the plating. Then use a contact cleaner, something like these - not only a "pure" contact cleaner, but also a "contact enhancer" : http://www.deoxit.com/ http://store.caig.com/s.nl/it.A/id.2527/.f http://store.caig.com/s.nl/sc.2/category.188/.f http://store.caig.com/s.nl/sc.2/category.292/.f Verify that the "spring effect" of the contacts is effective. jaclaz

Good plan. I quite frankly cannot see the point, unless you are using a very asymmetric compression engine, there is probably no practical use of having a compression algorithm that requires non-standard settings. However, it's your machine, your compression experiments, so good luck for 'em. jaclaz

The blinking is supported in "pure" DOS and In "full screen" mode only with ANSI, AFAICR: http://www.robvanderwoude.com/ansi.php Another possibility may be using a bash cmdline shell for NT, original bash does have blinking text supported. Check this one: http://www.claus-juergen-claussen.de/htmls/xewc_e.html it may have a similar effect to what you are looking for. jaclaz

@triger49 On another board, and in another life, I was known as "the Finder" For my ally is the Force. And a powerful ally it is. Life creates it, makes it grow. The Force surrounds us and binds us. Luminous beings are we not this crude matter. You must feel the Force around you. It is, my young padawan , but you are still young and fearful. Remember, a Jedi's strength flows from the Force. But beware. Anger, fear, aggression. The dark side are they. Once you start down the dark path, forever will it dominate your destiny. No! No different! Only different in your mind. You must unlearn what you have learned. Hmm. Control, control. You must learn control. Through the Force, things you will see. Other places. The future...the past...old friends long gone. jaclaz

Ok, I will then rephrase the original question : What the HECK are you compressing or uncompressing with 7zip to need that amount of RAM? jaclaz

I am sorry, but I cannot see the connection between the 400 Mb and the 4Gb (or if you want between the, say, 128 Mb needed to run a 32 bit PE 1.x and the 2Gb normally addressable) and the x64 command line. I mean, what command line program (available only in x64 build) doo you plan to use that needs more than 4000-400=3600 Mb of RAM? Have you checked the various PE 3.0 builds on boot-land? http://www.boot-land.net/forums/index.php?showforum=91 And/or the PE 1.x ones: http://www.boot-land.net/forums/index.php?showforum=52 Not at all my field, but I believe there are x64 based projects. jaclaz

A DOS driver needs to be loaded by config.sys, as sp193 tried telling you, and as I tried telling you by sending you to get the floppy which is properly set as an example and giving you the link to here: http://www.computing.net/answers/dos/dos-mass-storage-driver-usbaspisys/15261.html and as it is clearly stated in the article you found yourself: http://www.theinquirer.net/inquirer/news/1046069/yes-usb-drivers-dos Let's see if this is clear: If you need support in Windows98 (GUI) you need Windows98 drivers. If you need support in "pure" DOS (Command Line) you need DOS drivers. If you need support for GHOST you need NOT ANY driver, as GHOST has it's own ones. Yep. This is the part that will be difficult. In DOS you normally DO NOT "install" a driver (meaning there is NO install package for drivers, there is NO nice GUI - or command line for that matters - autoamgic utility, there is NOT a Registry, there is not a "standard" place for drivers, there is not a \System\ directory) , in DOS you "load" drivers by MANUALLY editing the config.sys and autoexec.bat (or like in the given example diskette, by using a driver loader program). So, you can have your drivers in: (just examples, I hope you get the idea ) You need to get clear this difference between "pure" DOS and the Win9x GUI you are used to, they work VERY differently. Start reading/learning: http://www.computerhope.com/msdos.htm http://www.computerhope.com/ac.htm http://www.tnd.com/camosun/elex130/dostutor1.html http://terpconnect.umd.edu/~nsw/ench250/dostutor.htm You need to grasp the basics before you will be able to customize your DOS system with drivers and the like. Since it is LIKELY that you will botch your current Windows 98 install by fiddling with DOS, it is strongly recommended that you use for practice a virtual machine and play a bit with DOS floppy images in a Virtual Environment (please read as Virtual PC v5.1 or earlier). jaclaz