Archive for November, 2009

USB printer using LPT1 port

Monday, November 30th, 2009

USER; Jonna (Has the following question)
Trying to print with USB printer using LPT1 port

THE SENARIO: – Looking for a little help from someone who can help me print to my USB printer using my LPT1 port? – We have an old genealogy software program that does not recoginze USB printers. Any ideas? – Thankyou!

USER; WhitPhil (responds)
DOS doesn’t recognize USB ports. – But, you can try this app. I haven’t tried it, but have seen it posted in another thread.

This blog is worth $0.00 – :)

Monday, November 30th, 2009


My blog is worth $0.00.
How much is your blog worth?

Root Nameserver

Sunday, November 29th, 2009

FROM – URL: http://en.wikipedia.org/wiki/Root_nameserver

A root name server is a name server for the Domain Name System’s root zone. It directly answers requests for records in the root zone and answers other requests returning a list of the designated authoritative name servers for the appropriate top-level domain (TLD). The root name servers are a critical part of the Internet because they are the first step in translating (resolving) human readable host names into IP addresses that are used in communication between Internet hosts.

OTHER LINKS; (Related to this topic)

#1: http://www.root-servers.org/

#2: http://www.isoc.org/briefings/019/

#2.2 http://www.isoc.org/briefings/020/

Q: Does all Internet traffic pass through the root name servers?
A: No Internet traffic passes through the root name servers at all. They have nothing to do with routing, note the difference in spelling. Name servers just answer queries from other parts of the DNS.

#3: http://k.root-servers.org/

#4: http://en.wikipedia.org/wiki/RIPE_NCC

Python

Saturday, November 28th, 2009

Python Beginners Guide for Non-Programmers

http://wiki.python.org/moin/BeginnersGuide/NonProgrammers

The World of DOS – Creating Batch Files

http://home.att.net/~gobruen/progs/dos_batch/dos_batch.html

Codecs

Friday, November 27th, 2009

This blog – has links to various codec downloads. (Looks entertaining)

Has the following links on this page.

#1: http://www.xpcodecpack.com/

#2: http://www.codecguide.com/

#3: http://www.divx.com/en/products/software/windows/divx

Ah Ha – Found some-thing that has eluded me, … #3:-Comment re-pasted below

DivX® 7 for Windows is a free download that provides everything you need to enjoy high-quality digital videos on your computer, including HD H.264 (.mkv) videos with AAC audio and videos created using all previous versions of DivX technology.

network-architecture

Thursday, November 26th, 2009

ADvertisement-From; >>>  ‘A’ Global Hosting Provider <<<

This is the sequence  of links that lead to a nice (flash-Video) overview/summary of this topic – which I liked enough, .. to post some links here.

#1: http://www.theplanet.com/
#2: http://www.theplanet.com/network/
#3: http://www.theplanet.com/network-architecture/
#4: http://www.theplanet.com/data-center-tour/

On the ‘Third-Section’ of this Virtual-Tour - There is a nice description about ‘mitigating’ DDOS attacks, which is interesting to know that there is something that can be done when this sort of attack is underway.

KEY-WORD: Googled – > Arbor peak flow < This leads onto a LOT of other stuff – LIKE ‘Comprehensive Threat Management‘ -, ..

#5: http://www.theplanet.com/network-operations-center/

Partitioning Tools (Like FDISK)

Thursday, November 26th, 2009

FDISK – The tool used to partition your harddisk, (which will enable the installation of ‘more-than-ONE’ operating system) GOOGLED – FDISK

Link #1: http://www.onecomputerguy.com/install/fdisk.htm

Link #2: http://en.wikipedia.org/wiki/Fdisk

Link #3: http://tldp.org/HOWTO/Partition/fdisk_partitioning.html

Link #4: http://www.fdisk.com/

Need more info on FDISK – refer to Google FDISK

Python – Lexical analysis

Wednesday, November 25th, 2009

A Python program is read by a parser. Input to the parser is a stream of tokens, generated by the lexical analyzer. This chapter describes how the lexical analyzer breaks a file into tokens.

Just interested in the “operators” towards the BOTTOM of the following url;  http://docs.python.org/dev/3.0/reference/lexical_analysis.html#id9

2.5. Operators

The following tokens are operators:

+       -       *       **      /       //      %
<<      >>      &       |       ^       ~
<       >       <=      >=      ==      !=

Carriage Return -/- Linefeed

Wednesday, November 25th, 2009

Carriage Return / Linefeed = CR/LF

These terms also have a number of different / other ways of being programmed, .. (And depending upon the angle it is being approached – they have different usage, Ie Web-Design, Vs System applications Programming.

Below is some links found connected with GOOGLING this term – CR+LF

#1: http://mc-computing.com/languages/CR_LF.htm

#2: http://www.websiterepairguy.com/articles/os/crlf.html

#3: http://www.acunetix.com/websitesecurity/crlf-injection.htm

That seems to provide enough information to satisfy what CR+LF is – (In terms of coding #1 – defines simply HOW cr/lf is coded) – There is not a comprehensive history about how all this came about. (Might add some more to this later) – The #2: Link does touch on the History very briefly, however is not indepth or definitive.

HISTORY OF CR/LF; Visit ~

#4: http://en.wikipedia.org/wiki/Newline

#5: http://www.rfc-editor.org/EOLstory.txt

NUMBER 5 (#5 – ab0ve) – Very Interesting (If your into this sort of thing) – I have pasted the first two paragraphs below – as this explains in part, EVERYTHING that I wanted to know.

The End-of-Line Story

The ASCII standard for text does not define a unique end-of-line (EOL)
character.  Instead, ASCII defines two independent and orthogonal
movements of the print head: Carriage Return (CR) and Line Feed (LF).
(IBM's EBCDIC did not make this mistake; it defined a single New Line
(NL) character.)  Early operating system designers had to adopt some
"end-of-line" convention using CR and LF; some used LF, some used
CR, and some used a two-octet sequence: LF CR or CR LF.

During the early ARPAnet research days (~1970-1972), this end-of-line
diversity among operating systems made network communication between
diverse host systems difficult.  After some discussion (recorded in
early RFCs), the researchers adopted a single convention:

	ASCII text transmitted across the network *must* use the
	two-character sequence:  CR LF.

The complete page is NOT very big, and well worth a read – (Think Ill go read it NOW!)

traditional replica of a 1930s Ford

Sunday, November 22nd, 2009

Kit price starting from $19,990 traditional replica of a 1930s Ford

Jeep_Forums – Gaucho

http://www.ultra-high-compression.com/fremont-tour.html