Hello dear guest!

Boot Land is a community driven pc software site established since 2006 and focused on recovery/backup boot disks, research of Microsoft Windows 2000/XP/2003/Vista/7 install/deployment/lease/antivirus/antispam tools, customizing Microsoft Windows PE administration systems and even learning how to recover computer data from disaster situations!

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)




Joined: 11-August 08
Profile Views: 8*
Last Seen: Yesterday, 06:45 AM
Local Time: Jun 17 2010, 01:35 AM 57 posts (0.08 per day)

kDn doesn't have a personal statement currently.

Personal Photo
Personal Info
Contact Information


Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Send Message
Contact Private

About Me
Files E2T
My Content
20 Dec 2009
Read Topic
fbinst.cmd script
I writen script to more simple using fbinst.exe.
You can dowload full version (as I use) or version without *.iso files (wich have big size).áNote: files cmdcons.iso, NERIH.GZ, OfflineNTPassword.iso, RusLive_RAM_Mini_2009.iso been replaced by "zero-files" to reduce the size of the archive fbinst_empty.7z.

The script was created to facilitate the work of fbinst and capabilities automate the process of creating a bootable flash drives.
Ie I have a course of action is:
1. Formatting (if necessary) and copy files to the zone (ud) with a script
2. Copying files to partition data
3. Thats all.

Now about the contents:
fbinst.cmd - the main script, the startup options [-h] - support, [--format] - formatting (if the zone (ud) is no, then the formatting is necessary), name of the device type (hdX)
Try run it with the -h and see everything for yourself. Without the --format format did not, therefore you do not ditch, if the formatting is enabled, be extremely careful with the choice of device. Killed with fbinst data on hard disk is not very easy to revive... And do not say that I did not warn you.
fbinst.txt - description of the commands and keys, you can look through the analog fbinst.exe -há
FbinstTool.exe - GUI for fbinst, unfortunately sometimes buggy. Still under development. The first time you get the Chinese language, but through the menu you can choose English.
format.cmd - script formatting submitted separately
format.ini - the formatting options to change here
extended\boot\*.* - floppy disk image and iso-files, to run from the extended (ud)á
extended\boot\splash\*.* - Splash and gfxmenu put here, again, for the extended (ud)á
menu\fb.txt - menu description fbinst, which you see when you start with stická
menu\readme.txt - a little HELP menu commands, translated from Chinese into English using Google translate
primary\*.* - files for the primary zone (ud), mainly for different boot loaders, while image disks can put and here. Iso-files put here is not recommendedá
syslinux\ldlinux.bin - syslinux-loader for a special approach, and therefore a separate directory.
All files in the directories (and subdirectories) extended\, primary\, syslinux\ will be placed in the zone (ud)á
There are some peculiarities. First about the zone (ud) besides from fbinst, FbinstTool grub4dos and no one knows, respectively, neither Windows, or Linux, or DOS from there no load can not, take this.
Second: for the normal operation of a loader ntldr boot.ini file you need to see the data (ie in the visible section), its contents can be like this:

[boot loader] á
default= C:\grldr  
[operating systems]
C:\boot\plop\plpbtldr.bin="PLoP Boot Manager 5.05"

Please note, this is a special ntldr with integrated ntdetect.com, normal ntldr from the zone (ud) will not work correctly if there ntdetect.com near boot.ini
Third: for syslinux in the visible area must be a directory /syslinux or /boot/syslinux with the relevant syslinux-files, and its configuration.

If not specified drive to work, it will be executed automatically attempt to find a USB-drive ... If the disk set forcibly, then no search will not run.
I honestly do not know how to behave automatic search if you use multiple flash drives simultaneously, but in any case, the script will wait for the latest USB-drive, so that the HDD connected to IDE or SATA drive, with automatic recognition is not exactly hurt)))

If the zone (ud) on a flash drive there, the request for formatting will not be issued ... Use in this case fbinst.cmd --format. Maybe you need to change the options in the file format.ini to save large files in the zone (ud).

Some images:

Files to download:
http://www.mediafire.com/file/yj0mw...pty.7z (2,40Mb)
http://www.mediafire.com/file/oytlmnijzgl/fbinst.7z (70,4Mb)
3 Mar 2009
Read Topic
[solved] grub4dos & memdisk bugreport
After "2009-02-13 fix problems booting Linux when there are mappings"
memdisk (from SysLinux ) not work.
Before 2009-02-13 memdisk worked OK.


title Memtest86
kernel /memdisk
initrd /BOOT/memtest86.wbt.gz

gzip image: decompressed addr 0x1ffd5000, len=0x00000000: failed
Decompression error: output buffer overrun

grub4dos-0.4.4-2009-03-03.zip & syslinux-3.73.zip not working also.

grub4dos-0.4.4-2009-03-04.zip - bug fixed smile.gif

No Information
Other Information
Country:: Ukraine
Last Visitors

23 May 2010 - 7:36

7 May 2010 - 8:21

2 May 2010 - 17:19

27 Mar 2010 - 12:24

28 Jan 2010 - 20:42
Other users have left no comments for kDn.
There are no friends to display.
* Profile views updated each hour