Image for Linux disks

[DrTeeth]

On Fri, 10 Feb 2012 09:28:56 PST, just as I was about to take a herb,
a1pcfixer disturbed my reverie and wrote:

>Whenever a new build is released I download all for which I'm
>licensed, rename, and store on a spare drive as well as my main PC.
>Never know when my main PC might be down & no web access.
>
>I put the version number into the file name to know which is newest on
>my storage drives.

Pheeeooow! I thought it was just me. I am forever renaming d/l files
to show the version numbers, to remove unnecessary rubbish like
'setup' and to give a file a name that means something - so many files
are called 'setup.exe'.

FWIW, my IfW is renamed 'Image for Windows (IFW, IFD-GUI, IFL-GUI)
v2.69.exe'. I also have a screen shot of my serial numbers stored too.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose to dance
in the puddles (Jewish proverb).

[a1pcfixer]

DrTeeth,

> I also have a screen shot of my serial numbers stored too.

LOL

I just post such into my passwords file and encrypt it......hoping I
don't develope amnesia anytime soon.{g}
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[Brian K]

TeraByte Support,

Any comment as to why files are missing from the IFL folder? See last post on Page 1.

[TeraByte Support(TP)]

TeraByte Support,

Any comment as to why files are missing from the IFL folder? See last post on Page 1.

Primarily because the zip file is used in both Linux and Windows, while of course the Windows install package is Windows-only.

Some of those files (the contents of config.zip, setup) are Linux-only files, and are included in the zip file, even though they serve no purpose in Windows. The remaining files are documentation files, and most of that material can also be found in KB articles, online tutorials, the IFL manual, or is only relevant in Linux.

In any case, none of the files you listed is functionally required in Windows.

[a1pcfixer]

I'd guess he's just trying to figure out the differences in the two;

Files created for IFL CD/DVD (from; iflnet.iso) during Windows
installation of file
[ifw_iflgui_en_setup_269.exe] {46.0MB}are......

"Z:\BOOT.CAT"
"Z:\INITRMFS.GZ"
"Z:\MENU.TXT"
"Z:\IFL.INI"
"Z:\ISOLINUX.CFG"
"Z:\VMLINUZ"
"Z:\ISOLINUX.BIN"
"Z:\FGGIOD.KTL"
"Z:\QWERTZ.KTL"
"Z:\QWERTY.KTL"
"Z:\AZERTY.KTL"
"Z:\DVORAK.KTL"


Whereas the files listed in stand alone [ifl_en_gui_269.zip]
{49.1MB} are.....

\ifl_en_gui_269\help
\ifl_en_gui_269\config.zip
\ifl_en_gui_269\iflnet.iso
\ifl_en_gui_269\makedisk.cfg
\ifl_en_gui_269\ifl_en_manual.pdf
\ifl_en_gui_269\makedisk.exe
\ifl_en_gui_269\setup
\ifl_en_gui_269\quickstart.txt
\ifl_en_gui_269\readme.txt
\ifl_en_gui_269\OS-Lic.zip
\ifl_en_gui_269\LICENSE.TXT
\ifl_en_gui_269\SYSLINUX.F35

Stand alone/second one is 3.1MB larger.
Subtracting iflnet.iso, the remaining 11 files don't equate
to the size difference between the two.
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[TeraByte Support(TP)]

But there you are comparing the size of iflnet.iso itself (46.3 MB) to the size of the stand-alone zip file contents (49.2 MB), which includes iflnet.iso plus approx 3 MB of other files. So the 3 MB difference it what I would expect to see.

Since the windows install file also contains IFD, TBIView, TBOSDT, and IFW, it's going to be larger than the stand-alone IFL zip file. In this case (v2.69 GUI), the Windows install file is about 56 MB.

Maybe I have missed your point, not sure....

[a1pcfixer]

Tp,

> But there you are comparing the size of iflnet.iso itself (46.3 MB)

No, I used ISO Buster to compare the CONTENTS of that ISO.

> Since the windows install file also contains IFD, TBIView, TBOSDT, and IFW, it's going to be larger than the stand-alone IFL zip file. In this case
(v2.69 GUI), the Windows install file is about 56 MB.

That's all irrelevant, I'm speaking of the IFL CD/DVD said (v2.69 GUI) 56MB file creates during execution (if user so decides).
When executed, it installs IFW, TBI View, mount as drive letter, etc. You also get the option of creating IFD & IFL CD/DVD's
which is what I'm speaking of.

Which creates the following;

"Z:\BOOT.CAT"
"Z:\INITRMFS.GZ"
"Z:\MENU.TXT"
"Z:\IFL.INI"
"Z:\ISOLINUX.CFG"
"Z:\VMLINUZ"
"Z:\ISOLINUX.BIN"
"Z:\FGGIOD.KTL"
"Z:\QWERTZ.KTL"
"Z:\QWERTY.KTL"
"Z:\AZERTY.KTL"
"Z:\DVORAK.KTL"
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[TeraByte Support(TP)]

Right, that is the contents of the CD/DVD = contents of iflnet.iso = approx 46 MB

That's exactly what I'd expect to see, so I'm not understanding where you see a descrepency.

The other listing you gave in the previous post was the contents of the stand-alone zip file, which includes iflnet.iso, plus 3 MB of other files.

[a1pcfixer]

Tp,

> The other listing you gave in the previous post was the contents of the stand-alone zip file, which includes iflnet.iso, plus 3 MB of other files.

Subtracting iflnet.iso, the remaining 11 files don't equate
to the size difference between the two.
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 Windows Vista Service Pack 2 build 6002

[TeraByte Support(TP)]

Once again, Jim, what you're showing me is what I'd expect to see.

My previous posts are the only way I can answer this...

Edit:
Unless you're referring to the small difference in size between iflnet.iso itself, which is 46.3 MB = 48,556,032 bytes, and the total size of the 12 files that it (and the IFL boot CD/DVD) contains, which is 46.0 MB = 48,182,611 bytes. That difference would be due to the ISO file system overhead within iflnet.iso, which causes that file to be slightly larger than the total size of the files it contains.

Which has nothing to do with any descrepancy between the stand-alone zip and windows install package. The same is true of both. The versions of iflnet.iso in the stand-alone zip, and the Windows install package, are identical, and they create identical (default) boot disks with the same total size of the 12 files.