BIBM 1.29a makedisk - creating a BIBM ISO file. I have made changes to the makedisk.cfg file (shown below) and have used it for years. Now, it appears that you/we have come up to the 2.88 MB disk image file size limit even for CD's. I there any way of getting around that limit easily? Any future plans?
Even with the change that I made to allow it to complete, I only have 381 bytes of disk space to play with. (my bui9 script file is 28,137 bytes in size)
my additions:
----------------------------------------------------------------------------------------------
[BIBM]
cdlabel=BOOTITBM
prod=BootIt Bare Metal
//opt1 was changed to save disk space ..... restorreg.tbs was removed
// tbs original: opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs;restoreg.tbs|Scripting Support
opt0=image.exe;cdboot.f35;cdboot.ins|Image for DOS (GUI)
opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs|Scripting Support
opt2=ICON16.DAT|Custom Icons
opt3=bootitbm.ini|BOOTITBM.INI file from local directory.
tbosboot.str_item1=\BOOTITBM
bootitbm.ini_opt2_title=Boot Options
bootitbm.ini_opt2_type=R
bootitbm.ini_opt2_v0=|&Normal
bootitbm.ini_opt2_v1="StartAt=2|&Partition Work"
// options added just in case option 0 was not selected
add0=IMAGE.EXE
add1=BUI9.TBS
Makedisk ran out of disk space copying files ....
-
- Posts: 3634
- Joined: Thu May 05, 2011 10:37 pm
Re: Makedisk ran out of disk space copying files ....
Do you burn to CD/DVD or if you do, do you care if it's bootable - if not
getting rid of cdboot.f35 can be done.
The USB option non-partitioned will use the full size of the USB stick -
booting depends on the BIOS.
When we come up against it (scripts larger, .exe grow) there is some size
that can be saved on the build, but not much so at that point it (BIBM) will
need to switch to a different booting mode (in order to include scripting
and disk imaging).
"tas3086" wrote in message news:9331@public.bootitbm...
BIBM 1.29a makedisk - creating a BIBM ISO file. I have made changes to the
makedisk.cfg file (shown below) and have used it for years. Now, it appears
that you/we have come up to the 2.88 MB disk image file size limit even for
CD's. I there any way of getting around that limit easily? Any future
plans?
Even with the change that I made to allow it to complete, I only have 381
bytes of disk space to play with. (my bui9 script file is 28,137 bytes in
size)
my additions:
----------------------------------------------------------------------------------------------
[BIBM]
cdlabel=BOOTITBM
prod=BootIt Bare Metal
//opt1 was changed to save disk space ..... restorreg.tbs was removed
// tbs original:
opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs;restoreg.tbs|Scripting Support
opt0=image.exe;cdboot.f35;cdboot.ins|Image for DOS (GUI)
opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs|Scripting Support
opt2=ICON16.DAT|Custom Icons
opt3=bootitbm.ini|BOOTITBM.INI file from local directory.
tbosboot.str_item1=\BOOTITBM
bootitbm.ini_opt2_title=Boot Options
bootitbm.ini_opt2_type=R
bootitbm.ini_opt2_v0=|&Normal
bootitbm.ini_opt2_v1="StartAt=2|&Partition Work"
// options added just in case option 0 was not selected
add0=IMAGE.EXE
add1=BUI9.TBS
getting rid of cdboot.f35 can be done.
The USB option non-partitioned will use the full size of the USB stick -
booting depends on the BIOS.
When we come up against it (scripts larger, .exe grow) there is some size
that can be saved on the build, but not much so at that point it (BIBM) will
need to switch to a different booting mode (in order to include scripting
and disk imaging).
"tas3086" wrote in message news:9331@public.bootitbm...
BIBM 1.29a makedisk - creating a BIBM ISO file. I have made changes to the
makedisk.cfg file (shown below) and have used it for years. Now, it appears
that you/we have come up to the 2.88 MB disk image file size limit even for
CD's. I there any way of getting around that limit easily? Any future
plans?
Even with the change that I made to allow it to complete, I only have 381
bytes of disk space to play with. (my bui9 script file is 28,137 bytes in
size)
my additions:
----------------------------------------------------------------------------------------------
[BIBM]
cdlabel=BOOTITBM
prod=BootIt Bare Metal
//opt1 was changed to save disk space ..... restorreg.tbs was removed
// tbs original:
opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs;restoreg.tbs|Scripting Support
opt0=image.exe;cdboot.f35;cdboot.ins|Image for DOS (GUI)
opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs|Scripting Support
opt2=ICON16.DAT|Custom Icons
opt3=bootitbm.ini|BOOTITBM.INI file from local directory.
tbosboot.str_item1=\BOOTITBM
bootitbm.ini_opt2_title=Boot Options
bootitbm.ini_opt2_type=R
bootitbm.ini_opt2_v0=|&Normal
bootitbm.ini_opt2_v1="StartAt=2|&Partition Work"
// options added just in case option 0 was not selected
add0=IMAGE.EXE
add1=BUI9.TBS
Re: Makedisk ran out of disk space copying files ....
Excellent, full answer. This is just one example of why Terabyte Unlimited is clearly ahead of your competition.
-
- Posts: 785
- Joined: Fri Aug 12, 2011 1:24 am
Re: Makedisk ran out of disk space copying files ....
I find that I can use almost any size USB flash drive to boot.
Some card readers will not allow me to boot from USB, though. No, it is
not a setting in the bios.
Mary
On 2/8/2015 9:29 PM, TeraByte Support wrote:
> Do you burn to CD/DVD or if you do, do you care if it's bootable - if not
> getting rid of cdboot.f35 can be done.
>
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
> When we come up against it (scripts larger, .exe grow) there is some size
> that can be saved on the build, but not much so at that point it (BIBM) will
> need to switch to a different booting mode (in order to include scripting
> and disk imaging).
>
>
> "tas3086" wrote in message news:9331@public.bootitbm...
>
> BIBM 1.29a makedisk - creating a BIBM ISO file. I have made changes to the
> makedisk.cfg file (shown below) and have used it for years. Now, it appears
> that you/we have come up to the 2.88 MB disk image file size limit even for
> CD's. I there any way of getting around that limit easily? Any future
> plans?
>
> Even with the change that I made to allow it to complete, I only have 381
> bytes of disk space to play with. (my bui9 script file is 28,137 bytes in
> size)
>
> my additions:
> ----------------------------------------------------------------------------------------------
> [BIBM]
> cdlabel=BOOTITBM
>
> prod=BootIt Bare Metal
>
> //opt1 was changed to save disk space ..... restorreg.tbs was removed
> // tbs original:
> opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs;restoreg.tbs|Scripting Support
>
> opt0=image.exe;cdboot.f35;cdboot.ins|Image for DOS (GUI)
> opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs|Scripting Support
> opt2=ICON16.DAT|Custom Icons
> opt3=bootitbm.ini|BOOTITBM.INI file from local directory.
>
> tbosboot.str_item1=\BOOTITBM
>
> bootitbm.ini_opt2_title=Boot Options
> bootitbm.ini_opt2_type=R
> bootitbm.ini_opt2_v0=|&Normal;
> bootitbm.ini_opt2_v1="StartAt=2|&Partition; Work"
>
> // options added just in case option 0 was not selected
> add0=IMAGE.EXE
> add1=BUI9.TBS
>
>
Some card readers will not allow me to boot from USB, though. No, it is
not a setting in the bios.
Mary
On 2/8/2015 9:29 PM, TeraByte Support wrote:
> Do you burn to CD/DVD or if you do, do you care if it's bootable - if not
> getting rid of cdboot.f35 can be done.
>
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
> When we come up against it (scripts larger, .exe grow) there is some size
> that can be saved on the build, but not much so at that point it (BIBM) will
> need to switch to a different booting mode (in order to include scripting
> and disk imaging).
>
>
> "tas3086" wrote in message news:9331@public.bootitbm...
>
> BIBM 1.29a makedisk - creating a BIBM ISO file. I have made changes to the
> makedisk.cfg file (shown below) and have used it for years. Now, it appears
> that you/we have come up to the 2.88 MB disk image file size limit even for
> CD's. I there any way of getting around that limit easily? Any future
> plans?
>
> Even with the change that I made to allow it to complete, I only have 381
> bytes of disk space to play with. (my bui9 script file is 28,137 bytes in
> size)
>
> my additions:
> ----------------------------------------------------------------------------------------------
> [BIBM]
> cdlabel=BOOTITBM
>
> prod=BootIt Bare Metal
>
> //opt1 was changed to save disk space ..... restorreg.tbs was removed
> // tbs original:
> opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs;restoreg.tbs|Scripting Support
>
> opt0=image.exe;cdboot.f35;cdboot.ins|Image for DOS (GUI)
> opt1=tbosdt.exe;tbexplo.tbs;setwindl.tbs|Scripting Support
> opt2=ICON16.DAT|Custom Icons
> opt3=bootitbm.ini|BOOTITBM.INI file from local directory.
>
> tbosboot.str_item1=\BOOTITBM
>
> bootitbm.ini_opt2_title=Boot Options
> bootitbm.ini_opt2_type=R
> bootitbm.ini_opt2_v0=|&Normal;
> bootitbm.ini_opt2_v1="StartAt=2|&Partition; Work"
>
> // options added just in case option 0 was not selected
> add0=IMAGE.EXE
> add1=BUI9.TBS
>
>
Re: Makedisk ran out of disk space copying files ....
creating "no partition" smaller than 2.8 works fine but ....
I have tried to create(makedisk) a USB larger than 2.8 MB without success. I continue to get the ran out of disk space writing file .... message. I have tried all the partition types, including no partition, on both a partitioned and un-partitioned USB flash drive. No Success. Do I need to change the USE288=1 option, or add another?
Any suggestions?
TeraByte Support wrote:
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
I have tried to create(makedisk) a USB larger than 2.8 MB without success. I continue to get the ran out of disk space writing file .... message. I have tried all the partition types, including no partition, on both a partitioned and un-partitioned USB flash drive. No Success. Do I need to change the USE288=1 option, or add another?
Any suggestions?
TeraByte Support wrote:
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
-
- Posts: 3634
- Joined: Thu May 05, 2011 10:37 pm
Re: Makedisk ran out of disk space copying files ....
I guess you could try
DIRECT=1
but can't guarantee it will work...
"tas3086" wrote in message news:9434@public.bootitbm...
creating "no partition" smaller than 2.8 works fine but ....
I have tried to create(makedisk) a USB larger than 2.8 MB without success. I
continue to get the ran out of disk space writing file .... message. I have
tried all the partition types, including no partition, on both a partitioned
and un-partitioned USB flash drive. No Success. Do I need to change the
USE288=1 option, or add another?
Any suggestions?
TeraByte Support wrote:
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
DIRECT=1
but can't guarantee it will work...
"tas3086" wrote in message news:9434@public.bootitbm...
creating "no partition" smaller than 2.8 works fine but ....
I have tried to create(makedisk) a USB larger than 2.8 MB without success. I
continue to get the ran out of disk space writing file .... message. I have
tried all the partition types, including no partition, on both a partitioned
and un-partitioned USB flash drive. No Success. Do I need to change the
USE288=1 option, or add another?
Any suggestions?
TeraByte Support wrote:
> The USB option non-partitioned will use the full size of the USB stick -
> booting depends on the BIOS.
>
Re: Makedisk ran out of disk space copying files ....
You guessed perfectly, It works great. Booting a 3.005 meg image.
Thank You.
TeraByte Support wrote:
> I guess you could try
>
> DIRECT=1
Thank You.
TeraByte Support wrote:
> I guess you could try
>
> DIRECT=1