Hi,
if i well remember with bootitNG it was possible to create a *.txt file with Name and registration key , and the Imagedisk automatically retrieved this info, during install. Is it possible to do the same with Boot it bare metal ?
Fabrizio
Installation Option
-
- Posts: 3641
- Joined: Thu May 05, 2011 10:37 pm
Re: Installation Option
when you run makedisk it asks for the name/key and applies it to the
bootitbm.ini file automatically for you.
"grisu70" wrote in message news:3322@public.bootitbm...
Hi,
if i well remember with bootitNG it was possible to create a *.txt file with
Name and registration key , and the Imagedisk automatically retrieved this
info, during install. Is it possible to do the same with Boot it bare metal
?
Fabrizio
bootitbm.ini file automatically for you.
"grisu70" wrote in message news:3322@public.bootitbm...
Hi,
if i well remember with bootitNG it was possible to create a *.txt file with
Name and registration key , and the Imagedisk automatically retrieved this
info, during install. Is it possible to do the same with Boot it bare metal
?
Fabrizio
Re: Installation Option
TBU support, that is not the same thing. I would also appreciate the facility to have a text file import of reg details. It is a relative PITA to a) find my reg details and b) copy and paste 2 separate pieces of info each time I want to make a disk.
I vote for bringing back the text file import of reg details too.
DrT
I vote for bringing back the text file import of reg details too.
DrT
-
- Posts: 3641
- Joined: Thu May 05, 2011 10:37 pm
Re: Installation Option
One of the fields is your name, so shouldn't have to copy/paste that,
however you can leave it all blank if you're just upgrading. You can also
always create a custom bootitbm.ini and leave it there and choose that.
"DrTeeth" wrote in message news:3367@public.bootitbm...
TBU support, that is not the same thing. I would also appreciate the
facility to have a text file import of reg details. It is a relative PITA to
a) find my reg details and b) copy and paste 2 separate pieces of info each
time I want to make a disk.
I vote for bringing back the text file import of reg details too.
DrT
however you can leave it all blank if you're just upgrading. You can also
always create a custom bootitbm.ini and leave it there and choose that.
"DrTeeth" wrote in message news:3367@public.bootitbm...
TBU support, that is not the same thing. I would also appreciate the
facility to have a text file import of reg details. It is a relative PITA to
a) find my reg details and b) copy and paste 2 separate pieces of info each
time I want to make a disk.
I vote for bringing back the text file import of reg details too.
DrT
Re: Installation Option
True about the name field, duh! That's what happens when one is sitting by a pool in Florida in the last few minutes of a holiday before setting off to the airport and heading home to London.
Personally, I still think the txt file approach is easier [wink].
DrT
Personally, I still think the txt file approach is easier [wink].
DrT
Re: Installation Option
TeraByte Support wrote:
>You can also
> always create a custom bootitbm.ini and leave it there and choose that.
>
That is a great piece of information.
I know you can use an ini when running makedisk.exe with both IFD versions but an ini doesn't work with IFL makedisk. Am I doing something wrong or is IFL an exception?
>You can also
> always create a custom bootitbm.ini and leave it there and choose that.
>
That is a great piece of information.
I know you can use an ini when running makedisk.exe with both IFD versions but an ini doesn't work with IFL makedisk. Am I doing something wrong or is IFL an exception?
-
- Posts: 3641
- Joined: Thu May 05, 2011 10:37 pm
Re: Installation Option
ifl is different, you'd have to have a custom .cfg file.
"Brian K" wrote in message news:3375@public.bootitbm...
TeraByte Support wrote:
>You can also
> always create a custom bootitbm.ini and leave it there and choose that.
>
That is a great piece of information.
I know you can use an ini when running makedisk.exe with both IFD versions
but an ini doesn't work with IFL makedisk. Am I doing something wrong or is
IFL an exception?
"Brian K" wrote in message news:3375@public.bootitbm...
TeraByte Support wrote:
>You can also
> always create a custom bootitbm.ini and leave it there and choose that.
>
That is a great piece of information.
I know you can use an ini when running makedisk.exe with both IFD versions
but an ini doesn't work with IFL makedisk. Am I doing something wrong or is
IFL an exception?