15 replies to this topic

[rrrh1]

Anyone looked at this ?

TeraByte OS Deployment Tool Suite
Free for Personal Use.
(See the License Agreement in the download for details)

Version 1.03a made available on Mar 15, 2008

http://www.terabyteu....com/tbosdt.htm

I have not downloaded it and checked the details.

The one that caught my attention was:

BootFile is a utility that enables to you boot an OS from a raw file (up to 4GB) containing a FAT/FAT32/NTFS file system .

rrrh1(arch1)

:-)

[rrrh1]

I guess using it in winbuilder is out:

Per license.txt

C. User may only use the Software in accordance with its
intended use as documented by TeraByte and distributed along
with the Software.

D. The Software may not be used to support any third party
product, nor create any tools or executable scripts for use
with any third party product, without the express written
consent of an authorized representative of TeraByte.

well it was a good thought...

rrrh1 (arch1)

:-)

[Brito]

Nice suggestion!

Can't we ask their permission?

Maybe they'll be nice and let it be used on our projects as they are also made available for free, who knows?

Why don't you try sending an email to see what they think?

[was_jaclaz]

http://www.boot-land...?showtopic=3722



jaclaz

[rrrh1]

---------------------------------------------------------------------
There are multiple licenses found in this document. The following
guidelines will help you determine which one applies to you:

The Freeware License Agreement applies only to individuals who will
use the Software for limited, non-commercial, purposes as described
within the Agreement.

The Trial Use License Agreement applies for a limited time for
individuals or organizations who wish to evaluate the software before
licensing.

The Full Use License Agreement applies to all individuals or
organizations not qualifying for either a Freeware or a Trial Use
License, and requires that such individuals or organizations have
purchased license rights to use the software.

---------------------------------------------------------------------

Their license seems to be complicated by the above.

=====================================================================
Freeware License Agreement
(Revised October 25, 2007)

PLEASE READ THIS AGREEMENT (THE "AGREEMENT") CAREFULLY BEFORE UPGRADING,
COPYING, INSTALLING, OR USING SOFTWARE FROM TERABYTE INC. ("TERABYTE").

WHEREAS, Terabyte is a vendor of software products, and

WHEREAS, the individual or entity using this product ("User") desires to
obtain the rights to use this product,

NOW, THEREFORE, in consideration of the mutual covenants and promises
contained herein, and for good and valuable consideration, Terabyte and
User agree that the foregoing recitals are true and correct, and agree as
follows.

I. Definitions

A. The Software
Computer software products owned by TeraByte, and computer
software products owned by suppliers of TeraByte, distributed
by TeraByte under agreement with the owners of such software,
which software products have been offered by TeraByte as
Freeware, i.e. available for use without payment of licensing
fees.

B. Media Fees
Such fees as may be charged by TeraByte to User, or by User
to third parties, to compensate for the cost of the media
used to transfer the Software.

C. License
The right for User to use the Software pursuant to the terms
and conditions defined herein. The absence of a license fee
shall in no way be an indication of a willingness or desire
on the part of TeraByte to place the Software in the public
domain. TeraByte intends to retain, and does retain, all
intellectual property and ownership rights in the Software.

D. Shrinkwrap Agreement
The unsigned agreement distributed with the Software defining
the standard terms and conditions under which the Software is
distributed and license granted.

II. Acceptance Of Terms

A. This agreement shall be accepted by User upon User's
performance of any of the following acts:

a. Installation, copying, or use of the Software on one or
more of User's computers;
b. Distribution of the Software to any party other than
Terabyte;
c. Retention of installable version of the Software for
more than fifteen (15) days; or
d. Any other act not consistent with non-acceptance of the
terms and conditions recited herein.

B. If User does not accept the terms and conditions recited
herein, User shall delete, return, and/or discard any files,
data, or materials associated with the Software.

C. If User has a License Agreement executed by an authorized
representative of TeraByte (and "Executed Agreement")
containing one or more terms and conditions which are
inconsistent with the terms and conditions contained in the
shrinkwrap license, then to the extent necessary, the terms
and conditions of the Executed Agreement shall supersede
those of the shrinkwrap license.

III. Scope of Use

A. User may use the Software on an unlimited number of
computers.

B. User may distribute the Software to third-parties only where
such third-parties are aware of, and agree to be bound by,
the terms and conditions contained in this Agreement. Such
distribution shall include all files associated with the
Software. Where User directs third-parties to download the
Software from TeraByte's website, User shall not provide a
direct download link, but shall direct such third-parties to
TeraByte's web pages so that such third-parties shall be
informed of TeraByte's policies and terms of use.

C. User may only use the Software in accordance with its
intended use as documented by TeraByte and distributed along
with the Software.

D. The Software may not be used to support any third party
product, nor create any tools or executable scripts for use
with any third party product, without the express written
consent of an authorized representative of TeraByte.

E. User may not modify the Software, any accompanying
documentation, or any file utilized in the delivery or
distribution of the Software or any accompanying
documentation, without the express written consent of an
authorized representative of TeraByte.

F. User may not reverse engineer, decompile, nor take any other
steps consistent with an attempt to reveal any confidential,
trade secret, or other non-public information associated with
the Software. Further, User may not assist any other party
attempting to reverse engineer, decompile, nor take any other
steps consistent with an attempt to reveal any confidential,
trade secret, or other non-public information associated with
the Software. Should User become aware of any activity in
violation of this term, whether or not under User's control
or authorization, User will inform TeraByte of such activity
and assist TeraByte in terminating such activity and
protecting its threatened rights.

G. User may not sell, rent, lease, or otherwise charge for the
distribution, installation, copying, or storage of the
Software, nor of any tools, scripts or other software
developed with the Software, other than a media fee as defined
herein.

H. User may not sell, rent, lease, distribute, or use the
Software, nor cause the Software to be sold, rented, leased,
distributed, or used, where such sale, rental, lease,
distribution, or use is prohibited by any statute or
governmental agency of the United States or other
international, national, or local entity having jurisdiction
at the point of sale, rental, lease, distribution, or use,
nor may User sell, rent, lease, distribute, or use the
Software where User is aware that such sale, rental, lease,
distribution, or use is likely to result directly or
indirectly in a sale, rental, lease, distribution, or use
prohibited by any statute or governmental agency of the
United States or other international, national, or local
entity having jurisdiction at the point of initial or
subsequent sale, rental, lease, distribution, or use.

IV. TERM AND TERMINATION

The terms and conditions of this Agreement shall remain effective
until this Agreement is terminated. Termination may be affected as
follows:

A. Termination by User. User may terminate this Agreement
at any time by destroying all copies of the Software,
as indicated below.

B. Termination by TeraByte.

a. TeraByte may terminate this Agreement at any point
upon notice to User if user, in TeraByte's sole
discretion, is in breach of any of the terms and
conditions contained herein, and fails to remedy
such breach within a reasonable period, but in no
event more than ten (10) days, following receipt of
such notice.
b. TeraByte may terminate this Agreement at any point
upon notice to User if TeraByte ceases to offer
Freeware licenses, or changes the terms and
conditions under which such licenses are offered,
and User is unwilling to accept the revised terms
and conditions.
c. TeraByte may terminate this Agreement at any point
should User's normal business operations be
disrupted or discontinued for mor than thirty (30)
days due to User's insolvency, bankruptcy,
receivership, or business termination.

Upon termination of this Agreement, User shall return, delete, or
destroy all copies of the Software, or any portion of the Software,
remaining in User's possession or under User's control, including all
distribution media containing distributable copies of all or any portion
of the software.

V. OWNERSHIP AND CONFIDENTIAL INFORMATION

TeraByte or its licensors own the Software under copyright, trade
secret and all other laws that may apply. All product names, designs,
and logos associated with the Software are trademarks of TeraByte. The
source code of the Software and all information regarding the design,
structure or internal operation of the Software are valuable trade
secrets of TeraByte or third parties with which TeraByte has licensing
arrangements ("Confidential Information"), provided however, that
"Confidential Information" shall not include information which otherwise
would be Confidential Information to the extent that such information was
publicly known or otherwise known to User previously to the time of
disclosure, which subsequently became known through no act or omission by
User, or which otherwise became known to User other than through
disclosure by TeraByte without violation of any party's obligations to
TeraByte. User shall not sell, transfer, publish, disclose, display or
otherwise permit access to any Confidential Information by any third
party, nor use any of the Confidential Information, except strictly as
part of the Software in the form originally distributed by TeraByte.

VI. Disclaimer of Warranty

The software and related documentation are provided "as is",
without warranty of any kind. TeraByte, Inc. disclaims all warranties,
express or implied, including, but not limited to, the implied warranties
of design, merchantability, fitness for a particular purpose. TeraByte,
Inc. does not warrant that the functions contained in the software or
documentation will meet User's requirements, or that the operation of the
software will be error-free, complete, or that defects in the software or
documentation will be corrected.

VII. Limitation of Liability

Under no circumstances shall TeraByte, Inc., nor any other person
or entity involved in the creation, production, or delivery of the
Software be liable for any lost revenue or profits or any incidental,
indirect, special, punitive, or consequential damages that result from
the use or inability to use the Software or related products or
documentation, even if TeraByte, Inc. has been advised of the possibility
of such damages.

Some states do not allow the limitation or exclusion of liability
for incidental or consequential damages so the above limitation or
exclusion may not apply. In no event shall TeraByte, Inc.'s total
liability to User for all damages, losses, and causes of action, whether
in contract, tort or otherwise, exceed the amount paid for the software,
including media fees.

VIII. HIGH RISK ACTIVITIES

The Software is not fault-tolerant and is not designed,
manufactured or intended for use on equipment or software running in
hazardous environments requiring fail-safe performance, including but not
limited to the operation of nuclear facilities, aircraft navigation or
communication systems, air traffic control, direct life support machines,
or weapons systems, in which the failure of the Software could contribute
to death, personal injury, or severe physical or environmental damage
("High Risk Activities"). TERABYTE AND ITS SUPPLIERS SPECIFICALLY
DISCLAIM ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS OF THE SOFTWARE FOR
HIGH RISK ACTIVITIES. TERABYTE DOES NOT AUTHORIZE USE OF THE SOFTWARE
FOR ANY HIGH RISK ACTIVITY. USER AGREES TO DEFEND AND INDEMNIFY
TERABYTE, AND HOLD TERABYTE HARMLESS, FROM AND AGAINST ANY AND ALL
CLAIMS, ACTIONS, LOSSES, COSTS JUDGMENTS AND DAMAGES OF ANY KIND IN
CONNECTION WITH USE IN RELATION TO ANY HIGH RISK ACTIVITY OF ANY COPY OF
THE SOFTWARE RELATING TO THIS LICENSE.

IX. GENERAL TERMS

A. ENTIRE AGREEMENT. This Agreement constitutes the entire
agreement between User and TeraByte in regard to the subject
matter herein, and supersedes all previous and
contemporaneous agreements, proposals and communications,
written or oral between the parties. No amendment of this
Agreement shall be effective unless in writing and signed by
duly authorized representatives of both parties.

B. NON-WAIVER. Waiver by TeraByte of any violation of any
provision of this License shall not be deemed to waive any
further or future violation of the same or any other
provision.

C. LAW AND JURISDICTION. This License and any dispute relating
to the Software or to this License shall be governed by the
laws of the United States and the laws of the State of
Nevada, without regard to U.S. or Nevada choice of law rules.
User agrees and consents that jurisdiction and proper venue
for all claims, actions and proceedings of any kind relating
to TeraByte or the matters in this License shall be
exclusively in courts located in Las Vegas, Nevada. If a
court with the necessary subject matter jurisdiction over a
given matter cannot be found in Las Vegas, then jurisdiction
for that matter shall be exclusively in a court with the
proper jurisdiction as close to Las Vegas as possible, and
within Nevada if possible.

D. SEVERABILITY. If any part or provision of this License is
held to be unenforceable for any purpose, including but not
limited to public policy grounds, then both parties agree
that the remainder of the License shall be fully enforceable
as if the unenforceable part or provision never existed.

E. NON-ASSIGNMENT. User may not assign this License without the
prior written consent of TeraByte, except, where User is a
commercial entity, as part of a sale of all or substantially
all of the assets of User's business.

F. NO THIRD PARTY BENEFICIARIES. There are no third party
beneficiaries of any promises, obligations or representations
made by TeraByte herein.

G. HEIRS AND ASSIGNS. This Agreement shall be binding on and
shall inure to the benefit of the heirs, executors,
administrators, successors and assigns of the parties hereto,
but nothing in this paragraph shall be construed as a consent
by TeraByte to any assignment of this agreement except as
provided hereinabove.

H. SURVIVAL. The provisions of paragraphs II.C, III.B, III.C-H,
V, VI, VII, VIII, and IX.A-C of this Agreement shall survive
any termination or expiration of this Agreement.

I am not sure legaly if this should be posted here.

I leave it up to the mods.

I do not see how we can use it without permission.

I will try to contact Terabyte Unlimited.

rrrh1 (arch1)
:-)

[rrrh1]

I have invited them here from their public newsgroup for their comments.

Maybe they will join up and let us know how they feel about our project.

rrrh1 (arch1)

:-)

[was_jaclaz]

Yes, the new kind of three ways license appears VERY interesting !

I guess this remains the only point that needs an authorization:

D. The Software may not be used to support any third party
product, nor create any tools or executable scripts for use
with any third party product, without the express written
consent of an authorized representative of TeraByte.

For Professionals, or to allow for a "wider" use by us hobbyist, the $15 seems to me a fair enough price.

jaclaz

[ktp]

BootFile is a utility that enables to you boot an OS from a raw file (up to 4GB) containing a FAT/FAT32/NTFS file system

Does it mean that you can prepare an USB key with it, then boot the key which in turn boots a disk image of a fully operational XP for example ?
(even if this image can only run on your system). If yes, then no more worries with BSOD 0x7B?
The HDD image could even be BartPE or WinPE/VistaPE ? How is the drive letter numbering etc... ?

[was_jaclaz]

Does it mean that you can prepare an USB key with it, then boot the key which in turn boots a disk image of a fully operational XP for example ?
(even if this image can only run on your system). If yes, then no more worries with BSOD 0x7B?
The HDD image could even be BartPE or WinPE/VistaPE ? How is the drive letter numbering etc... ?

NO, it means that you have to download the app and try it.





jaclaz

[ktp]

@jaclaz

NO, it means that you have to download the app and try it.

:-)
Well in fact before asking I already downloaded the package and quickly read the bootfile documentation.
But it will modify your MBR so I am not eager to try this. Maybe I can find a test machine for this.

Do you know a way to convert VMware vmdk format to RAW disk format ? I believe bootfile requires a RAW disk, and
I have a small vmdk XP image that can be tested.

[was_jaclaz]

Do you know a way to convert VMware vmdk format to RAW disk format ? I believe bootfile requires a RAW disk, and
I have a small vmdk XP image that can be tested.

Usually (it depends of the .vmdk format used) VMware images are actually RAW images with some sectors pre-pended to it.

Read this:
http://www.boot-land...?...ic=2220&hl=

You need to search, instead of the bootsector, for the MBR, that should begin with:
33C08ED0BC007CFB50

You can use Dsfo/DSfi or partcopy to copy only the trailing part to a new image once you know the right address.

jaclaz

[rrrh1]

Subject: Re: tbosdts with winbuilder
From: "TeraByte Support" <newssupport@terabyteunlimited.com>
Newsgroups: public.apps.tbosdts

Please contact TeraByte via email with details of what you're looking to do.

So is someone willing to help draft the e-mail ?

rrrh1 (arch1)

:-)

[ktp]

@jaclaz

Could you recommend a free hex editor capable of search/edit files or even edit disk ? Thank you.

[Brito]

I'm not jaclaz but maybe you like this freeware hex editor: http://www.softpedia...iny-hexer.shtml




-----------------

rrrh1:

Just try to explain your intentions regarding the use you plan to give on their tool and also mention that our work here is shared and distributed completely for free without restrictions.

Maybe pointing out a few links to the winbuilder.net page for reference also helps to get a better perspective.

[was_jaclaz]

You can also use gsar to find the address.

gsar -b -s:x33:xC0:x8E:xD0:xBC:x00:x7C:xFB:x50

jaclaz

[mr_]

This tools seams pretty interesting. I do not think it does work for operating systems which don't use BIOS for accessing the harddisk (only for bootstrap) but I would be glad to proven otherwise. It's pretty unlikely, in the folder dos_tbos there is no Windows or Linux device driver to accomplish this. These small exe, all together about ~1MB do not look like them can't.

The readme is only talking about an example of copying an existing DOS partition into a raw image file and boot this and a second example of creating a new raw image file containing tbos and booting this. Rather the comments about restoring the old MBR with autoexec.bat indicates that it's only desinged for DOS and tbos.

I wouldn't make such a big deal because of the MBR because an MBR can be stored inside a file and booted with grub4dos, rather backuping and restoring the MBR with third party tools or restoring grub4dos into MBR isn't a big deal.

On the other hand if it's only working for DOS / tbos then I do not see much need in this proprietary application as grub4dos does already support raw images and provides a BIOS service.

The readme always uses D:\ which might indicate that it's either working only for a second partition or second harddisk, I tested with C:\ and D:\ on second harddisk.

I've done my best in trying to get the examples to work but unfortunately always when I use bootfile x:\freedos.img or bootfile x:\tbos.bin then it shows just the help output. From the readme I thought I enter the commend correct...

Someone else got this application to work?

In hope not to have destroyed any interest in researching this application I post the readme here.

BOOTFILE
~~~~~~~~
BOOTFILE is a program that can be used to set up the MBR to boot an NTFS, FAT,
or FAT32 partition that is contained in a continuous file in an NTFS, FAT, or
FAT32 partition.

* The boot feature is available only in the Windows version of BOOTFILE.

* The file specified is expected to be 512 bytes larger than then actual
partition or file system size.

BOOTFILE is also used to restore the original MBR after booting.

* The MBR-restore feature is available in the Windows, DOS, and Linux
versions of BOOTFILE.

* When booting a partition using BOOTFILE, the MBR-restore should be
performed as soon as possible. For example, if using DOS, place the
"bootfile" MBR-restore command line in the first line of \AUTOEXEC.BAT;
or, if using TBOS, place the "bootfile.exe" command line in the first line
of \TBOS.STR (the .exe is needed).

NOTES:
~~~~~~
For Windows 9x platforms, the two DLLs included in the support directory
(TLIBR16.DLL and TLIBR32.DLL) are needed for BOOTFILE to function. These DLLs
should be placed in the same folder where BOOTFILE.EXE resides.

For Windows NT/200x/XP/Vista/etc.. platforms, BOOTFILE must be run in the context
of a user who is a member of the Administrators group for the local machine.

BOOT USAGE (Windows only):
~~~~~~~~~~~~~~~~~~~~~~~~~~
bootfile d:\filename [/keep] [/noui] [/noboot] [/bootunsafeifhung] [/bootunsafe]
[/retry] [/delay]

d:\filename -- [required] You must supply the full path to the file
name.

/keep -- [optional] This option is used to keep the existing
partition entries in the MBR. If this switch is used,
there must be at least one free entry in the partition
table for the emulated entry to be added. If this
switch is not used, then only the emulated entry will
exist in the partition table.

/noui -- [optional] This switch prevents the message box from
showing if a problem occurs. The errorlevel returned
by BOOTFILE can be used in a script to detect a problem.

/noboot -- [optional] This switch prevents the MBR from being
changed by the command, and also prevents the system
from being restarted when the command is run.

/bootunsafeifhung -- [optional] This switch forces a reboot even if the
system does not indicate that it is OK to shut down
(e.g. if some running program is hung or waiting for
user input). This switch may work the same as
/bootunsafe on newer versions of Windows. This switch
has no meaning if the /noboot switch is also used.

/bootunsafe -- [optional] This switch forces a reboot without asking
the system if it is OK to shut down. This switch has no
meaning if the /noboot switch is also used.

/retry -- [optional] Used to enable multiple retries when the
file system cache appears to not have been flushed.

/delay -- [optional] Wait 8 seconds after volume flush to ensure
file system cache has been flushed to disk.

MBR RESTORE USAGE (Windows only):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bootfile /RESTORE [/noui] [/ignoresig]

/noui -- [optional] This switch prevents the message box from
showing if a problem occurs. The errorlevel returned
by BOOTFILE can be used in a script to detect a problem.

/ignoresig -- [optional] This switch allows the saved MBR to be
restored even if the NT disk signatures do not match.


MBR RESTORE ONLY USAGE (DOS/Linux only):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bootfile [/noui] [/ignoresig]

/noui -- [optional] This switch prevents the message box from
showing if a problem occurs. The errorlevel returned
by BOOTFILE can be used in a script to detect a problem.

/ignoresig -- [optional] This switch allows the saved MBR to be
restored even if the NT disk signatures do not match.

REBOOT USAGE (All):
~~~~~~~~~~~~~~~~~~~
bootfile /REBOOT [/bootunsafeifhung] [/bootunsafe] [/ noui]

Reboots the computer.

/bootunsafeifhung -- [optional] Only applies to Windows and is described
above.

/bootunsafe -- [optional] Only applies to Windows and is described
above.

/noui -- [optional] This switch prevents the message box from
showing if a problem occurs. The errorlevel returned
by BOOTFILE can be used in a script to detect a problem.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
EXAMPLE BOOTFILE SETUP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As discussed above, the BOOTFILE utility can be used to boot a system from
a file system contained within a file. This section will give two examples
of creating such a file to be used by BOOTFILE.


Example 1: Start with a partition already containing a bootable copy of DOS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In this example, it's assumed we already have a partition containing a
bootable copy of DOS. The goal is to copy the DOS partition to a file,
and then boot from that file using BOOTFILE. The steps below will list
and explain the TBOSDT and BOOTFILE commands required to accomplish this.

1. Use TBOSDT to copy the DOS partition into a file:

copy partition 0 0x1 d:\partcopy.bin /b

The command line above runs the "copy partition" function to copy the
partition with ID 0x1 on hard drive 0 into the file d:\partcopy.bin.
The /b option adds 1 sector to the file in preparation for using it with
the BOOTFILE utility. That extra sector is used by BOOTFILE to save the
original MBR when the file is booted from. Note that partition ID numbers
can be determined for a given hard drive by using the LIST HD command in
TBOSDT. Example: list hd 0

2. Use TBOSDT to mount the file created in step 1 as drive 0:

mount 0: d:\partcopy.bin

3. Use TBOSDT to copy the *DOS/TBOS* version of bootfile.exe to the
mounted file system:

copy file bootfile.exe 0:

4. Use TBOSDT to create or modify the autoexec.bat file:

set textline 0:\autoexec.bat "bootfile.exe" /b

In the above command, the SET TEXTLINE command is used to insert the line
"bootfile.exe" in the autoexec.bat file. That line is necessary in order
to restore the original MBR after the file is booted from - so that the
next reboot will boot the system normally again.

If autoexec.bat already exists, the command will add the quoted text as the
first line in the file. If autoexec.bat does not already exist, the command
will create the file, and then write the quoted text to it. If desired, the
SET TEXTLINE command can be used to add/delete other lines in autoexec.bat at
this time.

5. Be sure to EXIT from TBOSDT at this point so that drive 0: is unmounted.
Exiting TBOSDT automatically unmounts the drive.

6. Run the *Windows* version of BOOTFILE to boot the system from the file:

bootfile d:\partcopy.bin (full path to partcopy.bin must be given)

The command above updates the MBR to boot from d:\partcopy.bin, and then
initiates a system reboot. Because of the way d:\partcopy.bin was updated
in steps 3 and 4, bootfile.exe and autoexec.bat will be in place, and booting
the file should be successful. On the next reboot, the system should boot
normally, the same as before.


Example 2: Create a FAT file system, prepare with TBOS, boot with BOOTFILE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In this example we will create a FAT file system in a file, prepare it to
boot into TBOS, and then boot the file with the BOOTFILE utility.

1. Use TBOSDT to create a new 32 MB FAT file system in a file:

add virtdrv d:\tbos.bin 32 TBOS /b

The above command creates a 32 MB file at d:\tbos.bin, formatted with the
FAT filesystem, and with "TBOS" as the volume label. The /b option adds one
sector to the file in preparation for use with the BOOTFILE utility.

2: Create a tbos.str file for TBOS:

set textline tbos.str "bootfile.exe" /b

The file tbos.str is the TBOS equivalent of autoexec.bat for DOS. In the
above command, the SET TEXTLINE command is used to create the file, and
then add the line "bootfile.exe" to it. That line is necessary in order
to restore the original MBR after the file is booted from - so that the
next reboot will boot the system normally again. If desired, SET TEXTLINE
can be used to add additional lines to the tbos.str - to execute other
commands as needed.

3. Install TBOS to the file, and copy required files to it at the same time:

tbossys /f d:\tbos.bin bootfile.exe tbos.str

This command will install TBOS to the file d:\tbos.bin, and then copy the
files tbos.str and bootfile.exe to the root directory of the FAT file system.
Note that for this specific example, the file bootfile.exe must be the
DOS/TBOS version of that file, since it will executed from TBOS.

4. Run the *Windows* version of BOOTFILE to boot the system from the file:

bootfile d:\tbos.bin (full path to tbos.bin must be given)

The command line above updates the MBR to boot from d:\tbos.bin, and then
initiates a system reboot into TBOS. When all commands listed in tbos.str
have been executed, TBOS will prompt you to reboot the system, which should
then boot normally, the same as before.

-----------------------------------------------------------------------------
End of document
----------------------------------------------------------------------------

PS:
Using the Windows version and tbos.bin I could now boot the tbos.bin (with hang). My harddisk (fortunately only VMware test machine) is now seen as empty.