jaclaz

I heard that it was written for 72 Hertz, instead . It would make more sense since 36, like 60, has more integer divisors than 35. jaclaz

You can use *any* hex editor, then. AFAIK the whole concept of "API" or "library" is post-DOS. There is a good (read only) library, called libregf, and of course you can "port to dos" hivex http://libguestfs.org/hivex.3.html There is the MS offline registry library, but AFAIK it is WINNT only, if you can use that from DOS, good for you: https://msdn.microsoft.com/en-us/library/ee210757(v=vs.85).aspx Again, if you actually DETAIL EXACTLY what you wish to achieve there may be other ways, command line usage of REGEDIT is perfectly possible for some scopes, as an example. jaclaz

You are right, sorry, my bad, (Mr.Presario made me do it ). No. (just the short version of "ontologically impossible"™ by dencorso). For an alternate meaning of "No", compare with: https://web.archive.org/web/20160527013035/http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html (that will allow the reply to be "Yes." as well) jaclaz

Well, the source code is provided, isn't that the "code" you were talking about? Or are you now asking a different thing, a pre-compiled "pure DOS" command line registry editor? What is the EXACT environment in which you wish to run that? Or describe what EXACTLY you wish to do. jaclaz

It is one of those errors that may be caused by *almost everything*, from a given antivirus/firewall not running properly to a corrupted file or filesystem, just as an example a known culprit is BitDefender: https://forum.bitdefender.com/index.php?/topic/75691-fixed-failed-to-connect-to-windows-service/ Unfortunately no way to know from just the message. Clear the System Event Log (optionally saving it before clearing it) then re-start/re-boot the computer and if the error presents itself again examine it or post a copy of it inside a .zip or .7z archive. Maybe with that data something more can be said about the possible causes. More generally (including the possible cause of the antivirus/firewall) it is definitely a timing problem of some kind during startup, *something* slows down the start of this (or that) service and then *somehow* *somethng* times out, a similar issue is known (and in some cases solved) by running: netsh winsock reset but it doesn't necessarily applies to your case. jaclaz

Sure. Meet the General Paul Lee Registry Viewer (which is also an editor): http://paullee.ru/ http://paullee.ru/regstry.html jaclaz

Yes, it is entirely possible that *something* in the install (or apply phase) doesn't like that second partition, Sure, if you create a new partition in diskpart it automagically creates a GPT disk (because it detects the bigger than 2.2 Tb disk and "switches mode"), but just after the "clean" command the disk should be actually "clean" . The idea was that on a "clean" disk you create the partition(s) in DOS or grub4dos, If you need to write the 55AA Magic Bytes, there should be no problems in initializing the disk in RPM, creating an arbitrary sized partition (without formatting it) and writing a MBR , then you write in grub4dos the new partition table. Or one could use cat --hex or this little script: http://reboot.pro/topic/18783-release-cateditg4b-script-to-write-hex-values/ I doubt that - outside diskpart - any PE, including the stupid Windows 10 derived one. will convert the disk to GPT if you only use the FORMAT command but of course when the good MS guys are involved everything is possible. jaclaz

Sure, we got that, but we tried being nice anyway . You see, when a new member comes on board we have no way to know how much knowledge and previous experience he/she has, I normally use my crystal ball (which has unfortunately given me a lot of tuning problems lately) and Tarots (I Ching for whatever reasons is less accurate), but I couldn't see that you had already tried each and every trick of the trade (+1) to attempt the recovery of that diskette. BTW, don't even think to make a grumpiness competition, not with me, I am the resident old grumpy bastard since 2004 or so, you simply have no chance to win. jaclaz

There were separate different releases for 9x/Me and NT family. jaclaz

If the OP actually has a DOS machine and a "real" floppy, an attempt to make a raw image of it (with the read only tab set) costs nothing or next to nothing. There is a particular program (not very famous) that over the years has proved to be very good, called Venus, some info (and more related tools) here: and in links therein. @98SE You would be surprised by the amount of "old" gear some MSFN members have. jaclaz

Well, of course if the disk is converted *automatically* to GPT, then it won't ever boot in BIOS. You clearly need a PE (and a diskpart) from Windows 7 or earlier (and as said earlier the whole point is about using a 32 bit OS). Maybe it is not the diskpart (or whatever) that *automatically* converts to GPT but something else in your process. If your "normal" process worked on a 3 Tb+ disk (in the past), by all means do that. Once you have a single partition working (and booting) normally, and the unallocated portion at the end, all is needed is to create the second partition (it is possible that the first partition needs to be slightly shrinked in order to have the first LBA sector of the second partition within the 2.2 Tb limit. More generally, the test is not about two partitions, it is about n partitions, with the ONLY requisite that the very last partition starts within the 2.2 Tb limit and does not extend for more than the same 2.2 Tb, i.e. the Start LBA of the LAST needs to be less than 2^32-1=4294967295 sectors and the amount of sectors in this last partition does not exceed 2^32-1=4294967295 In any case - re-thinking about this - all in all the experiment makes no real sense (making it with Windows 7 which already supports GPT), it makes sense for those OS's that know nothing about GPT. (we do have a few ways to boot a GPT disk on BIOS, if the OS supports GPT, like Windows 7 and later). jaclaz

Well, the diskpart txt seems just fine. Why didn't you format the second partition? I don't buy - with all due respect - that Windows doesn't boot. In the sense that *something else* (BIOS? or setting in it?) is preventing the booting. (i.e. the BIOS having some limitation with the hard disk size). Otherwise In the worst case, it would fail to boot with a bootBCD error (or however the error would come from the BOOTMGR). For all the code knows the active partition is within the 2.2 Tb limit, so the MBR code will chainload its PBR without issues and the PBR will chainload the BOOTMGR without issues. It is possible - in theory - (but very unlikely) that the presence of the second partition creates an issue, but I greatly doubt it. In any case, you can alway try to clear the second partition entry and try again. Even better, you could install a third party bootloader, like grub4dos to have more control in the booting phase. BUT right now, you can boot from the USB stick, and run grub4dos grub.exe from its DOS. At the grub> prompt, exchange drives: map (hd0) (hd1) map (hd1) (hd0) map --hook then try (reboot and restart, and re-map the drive if it doesn't work) 1) chainloader (hd0)+1 boot OR; 2) root (hd0,0) chainloader +1 boot OR: 3) root (hd0,0) chainloader /bootmgr boot jaclaz

It greatly depends on WHAT exactly are you running (I presume a PE of some kind) AND on HOW exactly you built the PE (from which sources). Had you actually READ the thread, you would have seen that Ntantor: had your same issue and solved it by using an updated version of imagex: jaclaz

And you tried making a copy or recovery of the diskette and you couldn't read it? Sometimes this may depend on a "too new" floppy disk drive or of a non-suitable program. A pure DOS machine may work better than any newer OS, of course with a good, internal, "vintage" floppy disk drive, not one of those el-cheapo USB external ones. jaclaz

An earlier version of the device or an earlier version of the driver? And of course we don't need just (L2), (L1) and (W1), we also need the L2S (source of L2), L1S (source of L1) and W1S (Source of W1), and the (L1S) and the (W1S) need to be the EXACT same version. I somehow suspect that the latter W1S one would be a tricky one to find. jaclaz

I am not even sure it allows you to. It seems like it sees the disk as being around 750 Gb. It is possible that you will need the "experimental" later version than 2.40, either 2.43 or 2.44, in any case you need to switch to LBA view (press F4). But you are running DOS, right? Get the latest grub4dos here: http://grub4dos.chenall.net/categories/downloads/ http://grub4dos.chenall.net/downloads/grub4dos-0.4.6a-2017-06-25/ http://dl.grub4dos.chenall.net/grub4dos-0.4.6a-2017-06-25.7z from the .7z archive extract just grub.exe and copy it to your DOS disk/diskette. Then run it. At the grub> command prompt, first determine the number of the disk you want to edit, In your RPM screenshot it is disk 2 (Ranish should number disks starting with 1, so it is second disk), in grub4dos notation that would be (hd1) (first disk is (hd0). Make sure that it is the right disk by typing: cat --hex skip=446 (hd1)+1 You should see all 00's and a final 55AA. If you don't see the 00's it means that you have the wrong disk or that you didn't clear the partition table entries. If you don't see the 55AA it means that the disk has not been (yet) initialized. If (hd1) is the right disk, run: partnew (hd1,0) 0x07 2048 4294965246 partnew (hd1,1) 0x07 4294967294 1258291200 makeactive (hd1,0) Then run: geometry (hd1) It should give you a Partition 0 and a Partition 1 both "filesystem unknown", and "partition type 0x07". If the disk is not initialized, just create a single primary partition NTFS in diskpart (size doesn't matter) and don't format it. Then you can go to grub, and after having checked as above, clear the partition with "partnew (hd1,0) 0 0 0" jaclaz

Oh, my ... jaclaz

PAC-laz's? Is it a spelling problem or an intentional mis-spelling (for *whatever* reasons)? jaclaz

Only to provide some more references, it should be this one: http://www.worldcat.org/title/wiring-circuit-planner-simulator/oclc/33029152 Maybe (just maybe) the actual simulator is the same included in this later CD http://www.worldcat.org/title/get-wired-wire-your-home-for-power-and-the-data-highway/oclc/33962894 jaclaz

Bur why that particular one? Isn't the (actually seemingly more easily available) ASRock 775i65G R3.0: a "better" choice? jaclaz

Not always, but often enough to originate this myth . jaclaz

I don't get it. Usher's suggestion is to NOT use any binary patch, including w98iopat.exe. Or if you prefer, using the patch is the NON-Usher suggestion : jaclaz

Then, get some cats or maybe weasels/martens, both have been used as pets or however domesticated animals by men at least since we have history to take care of mice and rats (and small snakes). jaclaz

jaclaz

I tend to prefer cats. jaclaz