jaclaz

Well, you are not planning to run DOS from the USB drive if I got it right. jaclaz

The "LOUSY" may be attributed to the otherwise very nice Victoria Author . The "no idea what to do" cannot. See if this helps (not latest version, though): http://docs7.chomikuj.pl/81583362,0,0,Victoria-for-Windows-v4.pdf The fact that the partition is seen as RAW may mean something or nothing, most probably all the head banging did unfortunately cause the expected worsening of the situation, or maybe the disk only warmed up a tadbit too much and only needs to cool down a bit. jaclaz

Wouldn't be easier and faster to know the answer by actually RUNning the presentation and see what happens? If I were you i would check your google, it does appear like broken. http://www.msofficeforums.com/powerpoint/5862-have-powerpoint-dynamically-update-excel-other-file.html http://skp.mvps.org/vba.htm http://skp.mvps.org/updtlinks.htm jaclaz

Hmm. Was it slimmed down by little green men overnight? Was it downloaded from the net pre-slimmed by an anonymous peep? In any case you are NOT having the same problem as the OP, who succesfully finished install and later could not log in to it. jaclaz

For the record, it isn't. The actual connector is the same. http://en.wikipedia.org/wiki/Parallel_ATA IDE is the very old name, since 1994 at least they should really be called ATA, and, to be picky, anything "optical" is ATA/ATAPI. SATA is actually Serial ATA, and to avoid misunderstandings previous ATA was renamed Parallel ATA or PATA. jaclaz

There is the 2M formats too. http://en.wikipedia.org/wiki/2M_(DOS) the max capacity on ED disks is (4 Gib is seemingly a bit too much ) +------------------------------------+ ¦ Double ¦ High ¦ Extrahigh ¦ +-------------------------------+-----------+-----------+------------+------+ ¦ Absolute record before 2M ¦ 820.0 Kb ¦ 1394.0 Kb ¦ -- ¦ ¦ ¦ Maximum 2M capacity (2MF /M) ¦ 902.0 Kb ¦ 1558.0 Kb ¦ -- ¦ 5.25 ¦ ¦ Minimum 2MGUI capacity ¦ 976.6 Kb ¦ 1639.8 Kb ¦ 1203.1 Kb ¦ (5¼) ¦ ¦ Physical limits (82 tracks) ¦ 1001.0 Kb ¦ 1668.2 Kb ¦ 1228.8 Kb ¦ ¦ +-------------------------------+-----------+-----------+------------+------¦ ¦ Absolute record before 2M ¦ 984.0 Kb ¦ 1722.0 Kb ¦ 2880.0 Kb ¦ ¦ ¦ Maximum 2M capacity (2MF /M) ¦ 1066.0 Kb ¦ 1886.0 Kb ¦ 3772.0 Kb ¦ 3.5 ¦ ¦ Minimum 2MGUI capacity ¦ 1176.0 Kb ¦ 1972.0 Kb ¦ 3944.0 Kb ¦ (3½) ¦ ¦ Physical limits (82 tracks) ¦ 1201.2 Kb ¦ 2002.0 Kb ¦ 4003.9 Kb ¦ ¦ +---------------------------------------------------------------------------+ jaclaz

Please note how that sentence may be understood as somehow stating that unlike their software, their hardware was excellent., which is IMHO quite a hazardous statement. I have no experience with actual "clik"'s, but my experience with some batches of (original) Zip drives (both actual drive and media) was at the time a nightmare. First 100 Mb ones usually worked very well. The "second edition" of the 100 and the first of the 250 Mb ones (if i recall correctly) were a nightmare. Heck, the clik got "promoted" to "Pocket.Zip" probably because of the above Click of death_ http://en.wikipedia.org/wiki/Iomega_Pocket_Zip_drive jaclaz

Yes, you can add it as the default allright. The /win95 (though it does NOT make any harm) can be removed allright. It is a provision for the original mind-boggingly complex way the good MS guys allowed triple boting among NT, MS DOS <=6.22 and Windows 95 (renaming io.sys to winboot.sys, etc.) The /win95 means "actually boot from WIN9x files and NOT from DOS ones" whilst the /win95DOS "actually boot form DOS files and NOT from the win9x ones", BOTH settings "ask NTLDR to cleverly rename a set of files, if the condition is verified", see here: http://home.earthlink.net/~jdbryan/directboot.html And of course you can change the description inside double quotes to anything you prefer. Glad I can count you among the happy bunnies . jaclaz

I don't need anything, thanks. I pointed you to a suggested procedure: http://reboot.pro/15040/page__st__8 I explained to you the REASONs why such a procedure is suggested (as opposed to "start imaging and let the program try again and again and again and again on bad sectors). If you had told datarescuedd to copy (just an example with very small numbers) sectors from 0 to 100, you would have as a result a file named image[0-51200].dd If this file, upon ispection, is actually 51.200 bytes in size, and you had no errors, you would be sure to have imaged correctly a chunk, and know exactly it's size and know exactly it's position. Then you go fo the next chunk, like 100 to 200 and you get another nice 51200 bytes file named image[51200-102400].dd, and so on. You chose the "other one", that's allright, I make no claim whatsoever that what was suggested was "right" and that what you did was "wrong", I am simply stating that you did another thing from what was suggested to you. On reboot.pro we even have an emoticon that in this case represents the poor HD arm/heads banging against an unreadable sector over and over: This is BAD for the hard disk and data integrity, and LESSENS probabilities of a successful image and of a later recovery. You just posted data that simply makes NO SENSE, whether these data appear nonsensical because they are plainly wrong or because something (whatever) went wrong during the imaging process (and whether this is connected to having done that in a way that was NOT recommended) is irrelevant, the result is that now you have "something" that you are not actually sure WHAT it is. To join files you need a file joiner. A good one (IMHO) is dsfi (part of the dsfok package: http://members.ozemail.com.au/~nulifetv/freezip/freeware/ jaclaz

Thanks. They contain what I needed, "original" ROOT directory entries for the various formats. I'll check and add this info. BTW, some (not so loosely connected) experiment: http://reboot.pro/15123/ jaclaz

While I wrote that with unmounted hives from other profiles in the same system, it of course applies to any unmounted hives, so certainly a mounted WIM image qualifies, too. With all due respect : RAWREG is unfinished (and severely bugged ) work The already mentioned Offline Registry uses a MS freely available Library and is command line, i.e. an exact correspondent to what was asked (command line editing). Whether a command line app is less friendly than a GUI app is of course well debatable. jaclaz

First paragraph is doable. Since you will boot FROM the USB bus, you will need NOT a "USB DOS driver", but rather an "USB boot manager/BIOS extension" (please read as "PLoP"). Will it work on that machine? Who knows? jaclaz

Not only , the problem is also that you don't have the faintest idea of WHAT you got (since you got it "randomly", i.e. without doing what was suggested you) Anyway I'll try to cheer you up for your loss. Rule Eleven: jaclaz

Just for the record, the Gimp has a price that cannot be beaten: http://www.gimp.org/downloads/ and no, I don't want to start the usual Gimp vs. Photoshop flamewar, just wanted to add the option for larryb123456. jaclaz

Version should be allright. Maybe it's a different issue, i.e. the PE *somehow* not getting the "right" sector size from the disk (or from the disk controller)? The "Advanced format" drives are 4096 bytes/sectors, right? OR, is the partition NOT at the beginning of the disk? http://technet.microsoft.com/en-us/library/cc766465(WS.10).aspx In other words, does this happen on a RAW disk when you run the EXACT command: create partition primary size=<size> offset=n align=1024 of course with the actual value for <size> or, if you prefer what happens if you only run: create partition primary size=<size> which alignment is created? jaclaz

Well, let's first try booting WIndows 98 with an "external" bootsector. Run bootpart as follows: BOOTPART WIN98 C:\BOOTSECT.W98 "Windows 98 added" Parameters explained: WIN98 <- use the bootsector for Windows 98 C:\BOOTSECT.W98 <- create a file named BOOTSECT.W98 on C:\ drive, containing the Windows 98 bootsector CODE and current partition bootsector DATA "Windows 98 added" <- create an entry in BOOT.INI with label "Windows 98 added" pointing to C:\BOOTSECT.W98 In other words, after you have run bootpart as per above, you will have an added entry in BOOT.INI like: C:\BOOTSECT.W98="Windows 98 added" Try rebooting and choosing it. Post what happens. jaclaz

Maybe you have the "wrong" (actually "right", but "old style" ) settings in the Registry? Compare with: http://www.911cd.net/forums//index.php?showtopic=21186&hl= http://www.911cd.net/forums//index.php?showtopic=21186&st=18 The manual way should have worked allright though: Which EXACT version of diskpart do you have running? jaclaz

A new approach : copy *everything* with XCOPY fast delete what you DO NOT need jaclaz

Yes/No. There are more files, though it is unlikely you will need to mount/modify them. (SECURITY and SAM), while it is possible that you will want to edit DEFAULT. http://msdn.microsoft.com/en-us/library/ms724877(v=vs.85).aspx Be aware (if needed) about HKEY_CLASSES_ROOT (that in ONline registry is actually a LINK to HKEY_LOCAL_MACHINE\SOFTWARE\Classes and does not exist OFFline) jaclaz

Nice! Hey, can I use this as Standard Reply #43 (an alternative to my standard reply #32)? http://reboot.pro/2587/page__st__1 I mean, without needing to pay you a fee for this? jaclaz

Heck, NO! CurrentControlSet DOES NOT EXIST at an OFFLINE Registry! When a NT system boots it checks the Registry key: HKEY_LOCAL_MACHINE\SYSTEM\Select and based on it's contents it creates a LINK named CurrentControSet that actually redirects to ControlSetxyz (normally it is ControlSet001 and normally there are only two ControSet's, ControSet001 and ControlSet002) jaclaz

Yes, you can. Can you use them simultaneously? jaclaz

Post a couple examples of tweaks that you have in "command line form". (and I presumme are targeted to "online" system). jaclaz

The entry: Is strange. Usually it points (to load Windows 98 or DOS) to a bootsector FILE. Yours points directly to the bootsector ON DISK. This should mean that you have "something else" (bootmanager/bootloader) that actually loads XP (or that I completely failed to understand how your setup is ). Anyway, your "C:" drive or however the same drive where BOOT.INI is should be FAT16 or FAT32 and ALSO contain in ROOT files IO.SYS, MSDOS.SYS and COMMAND.COM. Can you confirm this? If yes, all you have to do is get bootpart: http://www.winimage.com/bootpart.htm and use it to recreate BOTH a new bootsector file to boot Win98 AND a new entry in BOOT ini. just run bootpart in a command prompt window and post results. Read the (very short) bootpart.txt documentation, and, if you are sure about it's usage, just run it with the appropriate syntax or wait for instructions (based on the above output you get). jaclaz

The BCD is - in plain words - the "new" version of BOOT.INI, the actual configuration file that tells the Windows OS WHAT to boot (and WHERE to find it). Do take a few minutes here: http://www.multibooters.co.uk/bootmgr.html for the basics and here: http://www.multibooters.co.uk/multiboot.html where the boot process for both NT/2K/XP2003 (NTLDR+BOOT.INI) and Vista :ph34r:/2008/7 (BOOTMGR+\boot\BCD +WINLOAD.EXE) is explained graphically. Then check this: http://www.multibooters.co.uk/mbr.html and finally go on to read this: http://www.multibooters.co.uk/cloning.html The part: should be of particular interest to you , as well as the one about re-specializing the BCD. The "queer" thing, as said, is that the PC has XP as OS but a Vista (or 7) based recovery partition. You have to check if in the "small" partition you do have a BCDEDIT.EXE and see if it does run from XP or use one of the other mentioned BCD editors. jaclaz