Ah, so Windows 95 shortcuts weren't copying Unix, it was copying Mac OS aliases. Which were introduced in System 7, in 1991. Except that aliases still worked even if the target was renamed or moved to a different location, while shortcuts break.

QIC, Travan, Iomega Ditto, and DDS (DAT) tape drives were all marketed as consumer products in the 1990's.

In 2000 a DDS-2 tape cost $4.47, with a capacity of 8 GB (compressed): 56 cents per gigabyte. A 9.1 GB SCSI hard drive cost $385: $4.23 per gigabyte. Reusable optical media was not cost effective, and there wasn't anything else (that I can remember) with both high capacity and low cost.

(QIC and Travan drives were cheap, but the tapes were expensive; around $30 per tape IIRC. DDS tapes were cheap, but the drives were expensive; $700 for a DDS-2 drive in 1997.)

Yeah, but remember that inline statements didn't come until the addition of explicit scope delimiters. The most common form actually is:

perform routine-name
  until condition

and in that case, the UNTIL really does come at the end. But it still is really a PERFORM ... WHILE.

The fact is that this trips up programmers. They forget that they need to init the condition before the PEFORM, lest it never execute.

Standard COBOL (COBOL-85) has both DO WHILE and DO UNTIL loops. But UNTIL loops are actually WHILE loops: they test the exit condition before executing the loop.

If you really want an UNTIL loop you have to code extra syntax:

perform until condition with test after
  statements...
end-perform

with a lot of custom macros.

Remember that the despised Eolas patents (claiming invention of web site interactivity & plugins, including playing videos) were originally issued to the University of California, and then licensed to Eolas.

Compress with ZeoSync (100:1 lossless compression of random data). Repeat until compressed file is small enough to backup.

Because Apple first introduced the iDisk in 2000.

(iDisk was part of iTools, which became .Mac, then MobileMe, and finally iCloud. iDisk was dropped in iCloud, and the iCloud storage is not comparable in functionality.)

That's the catch. The standard Wireless Customer Agreement says that you can avoid the ETF if AT&T "increase[s] the price of any of the services to which you subscribe, beyond the limits set forth in your customer service summary" (emphasis added).

The Customer Service Summary (CSS) is the piece of paper that you get when you sign up, and is unique to you. You can download it from the online account.

The back page lists the estimated credits, adjustments, other charges, government fees and taxes. So you have no case as long as the fee actually imposed is less than the estimate in the CSS.

And guess what? My CSS from a year ago has a line item for "Other AT&T Surcharges" (for which there was no actual charge until now), and the estimated amount is higher than the new "Administrative" charge.

No wonder people who complain are told it isn't a breach of contract.

Isn't that because the USA taxes income, while other countries use a Value Added Tax (VAT)?

If that was true then why would it by fixed by installing an update to the other winsock LSP?

My guess is the other program was not implementing their LSP in full conformance to the API.

Parent is the most informative post in this entire topic.