Dev file?

Paul wrote in :

http://www.lg.com/lgecs.downloadFile...6116&ORIG INA
L_NAME_b1_a1=LG_440G_TRF_UG_Print_V1.2_130117.pdf& FILE_NAME=KROWM000466
116.pdf&TC=DwnCmd

That one is a PDF file. (Acrobat Reader)

LG_440G_TRF_UG_Print_V1.2_130117.pdf 1,570,311 bytes 122 pages



Got it! Thanks!

Boy, it sure is faster today with DSL working again.g


--
You know it's time to clean the refrigerator
when something closes the door from the inside.

CRNG wrote in
:

I was able to down load the above. Can you get it KenK?



Yep. DLed with DSL working again in a few seconds.

Unfortunately, I didn't check more than the first few pages displayed in
Foxit and ended up printing the many-paged Spanish version in the second
half of the file. Bet I'll be more careful next time!


--
You know it's time to clean the refrigerator
when something closes the door from the inside.

KenK wrote:
VanguardLH wrote in :

Have you tried opening it in NotePad to see if it is a text file?


Yes, it's mot.

There is a program here, ported from the Linux/Unix world,
which determines file type via examination of particular
bytes at particular offsets.

http://gnuwin32.sourceforge.net/packages/file.htm

Unfortunately, the dummies made it just about as difficult
as possible to install.

The executable ("file.exe"), needs to have a copy of the "magic"
file located in a parallel folder relative to the installation
point. It isn't sufficient to just throw a copy of "file.exe"
and the associated "magic" file into the same folder, as
the program will not look in its own folder.

That means, for analysis purposes, I have to move the data
file to be analysed, to the bin folder containing "file.exe".

The program gives a one-line output per file. It has
around a hundred different classifications for text files
for example, which can be a blessing or a curse, depending
on what you're doing. It can analyze a text file and
determine the line ending format is "mixed", with some
lines having CR-LF, and others just CR, or whatever.

It can detect PDF files.

And if there was such a thing as a DEV, it would
have an entry for it.

So if you don't like examining incoming files with a
hex editor, to get some idea what is inside, there is
"file.exe" to use for classification purposes. It is
not thrown off by file extension. For example, if I
take a PDF file and store it as "some.txt",

file.exe some.txt

some.txt: Acrobat PDF file

would be the result. It does not pay attention to the
extension, but does the determination itself. And the
"magic" file it uses, steers the classification process.

https://en.wikipedia.org/wiki/File_(command)

While it's possible to import a newer version of
a magic file (one with more classifications than the
one you've already got), I haven't bothered with that.
If I really really needed to know, I'd just boot a
modern Linux LiveCD and run the determination from there.

file /media/mount/WinXP/downloads/some.txt

some.txt: Acrobat PDF file

Installer files are a different matter, and getting
a classification like "Inno Setup" wouldn't tell you
a damn thing. So it doesn't scan a file at every
possible level.

HTH,
Paul

KenK wrote:

VanguardLH wrote:

Have you tried opening it in NotePad to see if it is a text file?

Yes, it's mot.

See my other reply (to your reply to Bill In Co). Looks like you
downloaded a device driver file from some unidentified site. The LG
site has the downloads for the user manuals (English and Spanish) and
they are PDF files, not DEV files. See my other reply for the URL.