You didn't say how it did not work. Anyway, the reason could be one of:
1. You got the wrong data of the partition boot blocks.
2. Bootlace.com executed without success.
3. You failed writing the data back to partition boot blocks.
4. You used an incorrect value of Y for the partition number. (Also check the correctness of S, H, B and C.)
5. The partition type is not supported, say, EXT4, reiser, etc.
6. The bootlace.com is buggy. (Try 0.4.5c if 0.4.6a failed.)
7. BIOS is buggy, it cannot access a partition beyond 128G limit.
8. Your MBR did not transfer the correct DL register(i.e., the drive number, usually 80h) to the partition's boot record.
9. Other unknown reasons.
And we will have to work on your definition of "long" (and of "advanced") if the 5 (five) lines you posted represent a "long" script written by an "advanced" user.
My friends, That was obviously a fun It is not a real script, It is a funny translation of these steps:
Step 1. Get the boot sectors of the partition and save to a file MYPART.TMP. For NTFS, you need to get the beginning 16 sectors. For other type of filesystems, you only need to get one sector, [...]
Step 2. Run this:
bootlace.com --floppy=Y --sectors-per-track=S --heads=H --start-sector=B --total-sectors=C --vfat --ext2 --ntfs MYPART.TMP
Step 3. Put MYPART.TMP back on to the boot sector(s) of your original partition (hdX,Y).
I apologize because I assumed members are all familiar with bash. I was going to reduce too much seriousness of discussion.
Neither I am advanced nor that script was long.
Anyway, thank you for letting us know how the project took a wrong direction some 7 years ago.
You went that wrong because I wasn't with you
Seriously now, what is the actual problem you are trying to solve ?
If you describe what the problem at hand is, I am pretty sure that people will try and assist you in solving it. .
Me in turn, appreciate the huge work done to reach this project to this point.
As an ordinary user, I feel I should help the project by test, bug report or feature request. I cannot already help coding or patching. Though prizing is needed and effective, but I believe the main factor who improves a work is criticism.
I requested my dear friends to re-establish the /usr/local/bin/grub, but its up to you to do or not. Everyhow, I use the program for its rich capabilities and usages.
Cheers to you all, Thanks for helps
Edited by Bahram_Alinezhad, 18 September 2016 - 05:00 PM.