As is my usual practice, I create an ISO for IfL when installing Image
for Windows.
The issue is, in spite of entering the correct registration details
(twice), when IfL loads, it asks for my registration details.
In all the years I have been using Image I have never come across this
before. How can I fix it please?
--
Cheers,
DrT
** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.
IfL registration issue
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: IfL registration issue
Which version of IFL (CUI or GUI)?
What options are you using to create the ISO?
Are you booting the ISO directly and seeing the issue (e.g. booting it in a VM)? Or are you booting the ISO from through a boot loader (e.g. a UFD with multiple ISO files you can select to boot from a menu)?
I'm not seeing any issues with a normal MakeDisk ISO created with IFL GUI 3.18 and booted in a VM.
What options are you using to create the ISO?
Are you booting the ISO directly and seeing the issue (e.g. booting it in a VM)? Or are you booting the ISO from through a boot loader (e.g. a UFD with multiple ISO files you can select to boot from a menu)?
I'm not seeing any issues with a normal MakeDisk ISO created with IFL GUI 3.18 and booted in a VM.
Re: IfL registration issue
On Wed, 16 May 2018 15:54:21 EDT, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:
>Which version of IFL (CUI or GUI)?
3.18 GUI x64. I usually use the 32 bit with networking.
>What options are you using to create the ISO?
I do not mean to sound sarcastic in any way, but the answer to the
question is exactly the same ones I have always used for ages, I go
the customised route and select align on 1MB boundaries. I use
makedisk in windows (8.1 - x64)
>Are you booting the ISO directly and seeing the issue (e.g. booting it in a VM)? Or are you booting the ISO from through a boot loader (e.g. a UFD with multiple ISO files you can select to boot from a menu)?
I am booting IfL in a flash drive after getting into my PC's boot
device selection menu.
>I'm not seeing any issues with a normal MakeDisk ISO created with IFL GUI 3.18 and booted in a VM.
I have never seen this in all the years I have been using your
excellent backup products. As IfL is about 5 times faster than IfD on
my PC, I am anxious to get the issue resolved.
I mage the flash drive twice just in case I had forgotten something,
but I hadn't.
I am going to make another flash drive with the 32 bit and will report
back to this thread.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
TeraByte Support(PP) disturbed my reverie and wrote:
>Which version of IFL (CUI or GUI)?
3.18 GUI x64. I usually use the 32 bit with networking.
>What options are you using to create the ISO?
I do not mean to sound sarcastic in any way, but the answer to the
question is exactly the same ones I have always used for ages, I go
the customised route and select align on 1MB boundaries. I use
makedisk in windows (8.1 - x64)
>Are you booting the ISO directly and seeing the issue (e.g. booting it in a VM)? Or are you booting the ISO from through a boot loader (e.g. a UFD with multiple ISO files you can select to boot from a menu)?
I am booting IfL in a flash drive after getting into my PC's boot
device selection menu.
>I'm not seeing any issues with a normal MakeDisk ISO created with IFL GUI 3.18 and booted in a VM.
I have never seen this in all the years I have been using your
excellent backup products. As IfL is about 5 times faster than IfD on
my PC, I am anxious to get the issue resolved.
I mage the flash drive twice just in case I had forgotten something,
but I hadn't.
I am going to make another flash drive with the 32 bit and will report
back to this thread.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: IfL registration issue
Some users create customized builds. I asked so I could run a test using the same build options. In any case, I didn't see an issue using a UFD with normal builds of IFL GUI 32-bit or 64-bit.
Can you check if the updated ifl.ini file is getting into the build? After booting to IFL, start a Terminal and run the following command. Do you see your name and key in the file (you should also see the "GlobalGeoAlign2K=1" option since you set align on 1MB)?
cat ifl.ini
Can you check if the updated ifl.ini file is getting into the build? After booting to IFL, start a Terminal and run the following command. Do you see your name and key in the file (you should also see the "GlobalGeoAlign2K=1" option since you set align on 1MB)?
cat ifl.ini
Re: IfL registration issue
On Thu, 17 May 2018 12:38:54 EDT, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:
>Some users create customized builds. I asked so I could run a test using the same build options. In any case, I didn't see an issue using a UFD with normal builds of IFL GUI 32-bit or 64-bit.
>
>Can you check if the updated ifl.ini file is getting into the build? After booting to IFL, start a Terminal and run the following command. Do you see your name and key in the file (you should also see the "GlobalGeoAlign2K=1" option since you set align on 1MB)?
>
>cat ifl.ini
I understand why you asked for the details of how I configure IfL. The
1MB boundary option is the only one I change. I use the maximum custom
options.
I cannot run the test you ask as I cannot type in the Terminal. That
is how I used to reboot. Could you please tell me where the ini file
should be so I can check in windows?
I really appreciate the help and really was not trying to be funny
earlier on. That is how my prose comes across sometimes though.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
TeraByte Support(PP) disturbed my reverie and wrote:
>Some users create customized builds. I asked so I could run a test using the same build options. In any case, I didn't see an issue using a UFD with normal builds of IFL GUI 32-bit or 64-bit.
>
>Can you check if the updated ifl.ini file is getting into the build? After booting to IFL, start a Terminal and run the following command. Do you see your name and key in the file (you should also see the "GlobalGeoAlign2K=1" option since you set align on 1MB)?
>
>cat ifl.ini
I understand why you asked for the details of how I configure IfL. The
1MB boundary option is the only one I change. I use the maximum custom
options.
I cannot run the test you ask as I cannot type in the Terminal. That
is how I used to reboot. Could you please tell me where the ini file
should be so I can check in windows?
I really appreciate the help and really was not trying to be funny
earlier on. That is how my prose comes across sometimes though.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
-
TeraByte Support(PP)
- Posts: 1646
- Joined: Fri Aug 12, 2011 12:51 am
Re: IfL registration issue
Boot to IFL normally. Once at the desktop, click the "Terminal" icon on the icon bar (last one on the right). Then run the command to show the contents of the file.
The ifl.ini file gets packed into the build. It's not usually easily accessible in Windows, unless you have Windows utilities that will work with the Linux files. In Linux you can open the initrmfs.gz file, then the initrmfs file, then browse the tbu folder and see ifl.ini. Since you can boot IFL it's probably easier to check that way.
The ifl.ini file gets packed into the build. It's not usually easily accessible in Windows, unless you have Windows utilities that will work with the Linux files. In Linux you can open the initrmfs.gz file, then the initrmfs file, then browse the tbu folder and see ifl.ini. Since you can boot IFL it's probably easier to check that way.
-
Bob Coleman
- Posts: 786
- Joined: Fri Aug 12, 2011 5:58 pm
Re: IfL registration issue
I assume by registration details you are talking about your name and key. Do you/did you enter those when asked by Makedisk?
Re: IfL registration issue
On Thu, 17 May 2018 14:20:01 EDT, just as I was about to take a herb,
Bob Coleman disturbed my reverie and wrote:
>I assume by registration details you are talking about your name and key. Do you/did you enter those when asked by Makedisk?
My original message reveals all
. In short, the answer it "yes".
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
Bob Coleman disturbed my reverie and wrote:
>I assume by registration details you are talking about your name and key. Do you/did you enter those when asked by Makedisk?
My original message reveals all
. In short, the answer it "yes".--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
Re: IfL registration issue
On Thu, 17 May 2018 13:22:45 EDT, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:
>Boot to IFL normally. Once at the desktop, click the "Terminal" icon on the icon bar (last one on the right). Then run the command to show the contents of the file.
I cannot type in terminal. My £100 USB keyboard does not seem to work
in IfL.
>The ifl.ini file gets packed into the build. It's not usually easily accessible in Windows, unless you have Windows utilities that will work with the Linux files. In Linux you can open the initrmfs.gz file, then the initrmfs file, then browse the tbu folder and see ifl.ini. Since you can boot IFL it's probably easier to check that way.
I'll make an ISO and boot into Linux and see what I can find. I'll
report back.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
TeraByte Support(PP) disturbed my reverie and wrote:
>Boot to IFL normally. Once at the desktop, click the "Terminal" icon on the icon bar (last one on the right). Then run the command to show the contents of the file.
I cannot type in terminal. My £100 USB keyboard does not seem to work
in IfL.
>The ifl.ini file gets packed into the build. It's not usually easily accessible in Windows, unless you have Windows utilities that will work with the Linux files. In Linux you can open the initrmfs.gz file, then the initrmfs file, then browse the tbu folder and see ifl.ini. Since you can boot IFL it's probably easier to check that way.
I'll make an ISO and boot into Linux and see what I can find. I'll
report back.
--
Cheers,
DrT
"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill
Re: IfL registration issue
Hi,
I was not successful in opening the initrmfs file. I have not found any information on this whilst searching either.
--
Cheers
DrTeeth
I was not successful in opening the initrmfs file. I have not found any information on this whilst searching either.
--
Cheers
DrTeeth