28 replies to this topic

[dencorso]

I cross-posted it on original thread:
http://www.911cd.net...o...1702&st=241

Thanks, jaclaz! I have updated the KillCHS program to v. 1.2, by incorporating Icecube's suggestions (thanks, Icecube!), and revising a little more the whole code. The new version is now in place of the former, still in post #22, so that your posted link remains valid. You both rock!
Side note: The source code remains not consistently formatted, but is nevetheless, a little better, visually.

[online]

@ktp
Not sure if the patching at every boot-up could be useful in your case...
Please, see here
http://www.boot-land...?...ost&p=73826

[calfared]

For what it's worth, here I offer the boot-land community my revised version of Clemens Fruhwirth's KillCHS utility, both compiled and as source code, alongside with Fruhwirth's original code renamed killchs.ori, to help those interested in determining what I added to the code. My revised version can patch the NTFS boot loader and both flavors of the FAT-32 NTLDR boot loader (viz. MSWIN4.1 and MSDOS5.0). It has been compiled with djgpp's gcc 4.10 and runs in the NT-family Windows OSes, in Win 9x/ME and in plain DOS (but CWSDPMI is required).
Usage is simple:
KillCHS <filename.ext>
It will crash, however, if run without providing a filename.
Update (Aug 01, 2009): I've incorporated Icecube's suggestions (in post #24, below) and revised further the code. The new version (1.2) is more user-friendly, and only accepts one parameter, but it'll just complain and do nothing in case none or more are provided in the command line, instead of crashing on none and ignoring all parameters but the first, when more than one is provided.
Attached File(s)
KillCHS.7z (34.59K)
Number of downloads: 250

Forgive my ignorance, but how you use it? I'm having problem of "missing NTLDR" and informed me that it could solve.

Thanks

Edited by calfared, 18 July 2011 - 06:12 PM.

[Wonko the Sane]

Forgive my ignorance, but how you use it? I'm having problem of "missing NTLDR" and informed me that it could solve.

Thanks

calfared, it doesn't work like this .

I told you here:
http://reboot.pro/14961/
that that was a possible cause.

The general idea is that ONCE we know (because you are so kind as to post the required info):

• the EXACT error
• the EXACT configuration you have
• the EXACT hardware you have

the issue can be solved by this or by ANOTHER fix, since the CAUSE is another one.
In any case, as told you, it is possible that some fixes are needed in the partition table of the MBR, anyway.
(or it is possible that the cause is a completely different thing, so that it needs a completely different fix).

Right now we are still in the "I'm ill Doctor, Help!" stage, reference:
http://homepage.ntlw...ard-litany.html

Start a new thread.

• Describe EXACTLY what you did.
• Describe EXACTLY the behaviour you are getting.
• Describe EXACTLY what you are trying to achieve.
• Describe EXACTLY the hardware you are using.

This way someone will be able to actually help you solve your problem, as opposed to make guesses (educated , but still guesses) about what your problem may be and what solution you may find for it.

Anyway the little program is made to patch a bootsector, that you need to extract from the actual Volume, and after the patch, re-write to the proper location (first sector of volume).
You can do the patch manually, with a normal hex/disk editor (such as Tiny Hexer) following the info given in the referenced "original" thread here:
http://www.911cd.net...ic=21702&st=129


Wonko