Hmm, my grandmother gets connections in the 54-56K area (yes, faster than the FCC allows) consistently. Of course, Conexant-based Winmodems didn't work well with my former ISP. The fastest I got normally was 26K! (Of course, when the lines were cleaned in preparation for ADSL, I got a small speed increase) Quick question, though. Does anyone know whether the newer V.92 standard hits 56K upstream? I know it lets you connect to the ISP faster, and offers internet call waiting. Of course, there's also the Emerson Switchboard, which I suspect is a box with 5 V.92 56K modems. I assume you dial in to IT, and then it calls your destination.
Of course, I see more uses than sharing for this. I hope you all remember Blaster. A firewall was a good alternative defense against Blaster (not saying that patching is a bad idea, but you'd probably get all of the patches anyway if you saw how many there were, and over a 56K modem, that's ridculously slow...) AFAIK, this also acts as a firewall. Just think of a cable/dsl modem with a built in router/firewall. Now, take out the cable/dsl modem, and put in a 56K modem. Damn useful, isn't it?
No, it wasn't Daytona. From a Windows Server 2003 history on Paul Thurrott's SuperSite for Windows, here's some info on Daytona:
The next release, Windows NT 3.5, was code-named Daytona, and shipped in September 1994. "Daytona was a very rewarding project," Thompson said. "We focused on size and performance issues, and on "finishing" many of the first-release features of 3.1. Daytona also had significant functional improvements and enhancements." The original themes for Daytona were size, performance, compression, and Netware compatibility. Two of those goals were emblematic of the time: DoubleSpace-style compression was a hot topic in the early 1990's because disk space was at such a premium, and Netware was the dominant network operating system of the day. "We eventually dropped compression," Thompson said, "but the Netware port was strategic. Novell was ambivalent about the NT desktop ? they didn't know if they wanted to build a client. We offered our assistance, but they kept messing around and... well. We did our own. And it just blew them away. Ours was the better Netware client, and customers used ours for years, even after they finally did one. That client enabled the NT desktop, because Netware was the prevalent server in the market. We wouldn't have been able to sell NT desktops otherwise."
Daytona also benefited from new compiler technology which enabled Microsoft to compress the code size and enable realistic NT desktops on lower-end systems than the original version. "The results were measurable," Thompson said.
Windows NT 3.51 was dubbed the Power PC release, because it was designed around the Power PC version of NT, which was originally supposed to ship in version 3.5. But IBM constantly delayed the Power PC chips, necessitating a separate NT release. "NT 3.51 was a very unrewarding release," Thompson said, contrasting it with Daytona. "After Daytona was completed, we basically sat around for 9 months fixing bugs while we waited for IBM to finish the Power PC hardware. But because of this, NT 3.51 was a solid release, and our customers loved it." NT 3.51 eventually shipped in May 1995.
Wasn't Cairo released in 1996 or something? BTW, I don't think MS wants your money for Cairo anymore. They'd rather have your money for at least Windows 2000, if not XP or Server 2003.
BZZT! It WAS Windows NT 4.0. Here's a FOLDOC entry on NT4:
Windows NT 4
A version of Microsoft's Windows NT operating system, originally code named "Cairo". It was supposed to ship in the first half of 1995. Details are scarce, but it is intended to provide an object-oriented version of Windows.
They do a bad job of cheating. Ever try transparency in Konsole? It's not showing you what's directly behind your Konsole, it's showing you your desktop background.
Re:Well now, that's just great.
on
Xr Renamed to Cairo
·
· Score: 0, Offtopic
Hmm, I didn't think anything before Windows 2000 supports alpha-blending. You are talking about Windows NT 4 (code name Cairo), right?
Most AOLusers will be using either AOL's browser or IE4/5/6. TinyURL has a toolbar button. Clicking it in IE4/5/6 will automatically use the URL of the page in question, and copy it to the clipboard in IE4/5/6. Even an AOLuser can figure that out. Unfortunately, it doesn't work in anything that ISN'T IE.
Mini-itx isn't port layout compatible with most *ATX boards anyway (or, for that matter, other mini-itx boards)... CardBus should be there... There should be a keyboard/pointing device standard. Drop a kb/pd combo (toshiba/nec/winbook layout with nipple, for example - my favorite) in, and go. Don't like the kb/pd from your new Dell? Sell it and buy something else... A widescreen case branch (sub-branches for 15.4" and 17") should exist. Everything should drop in then be held in by a couple screws. Including the top of the case (4 screws?). Put the mobo, hdd, and cd-rw/dvd (and port card or Mini-PCI/AGP cards) on the tray (which already has a PSU, prewired), screw it down, throw on the top of the case, screw it down, pop on the kb/pd, screw it down, and pop on the LCD and screw it down. If you want, drop the whole thing on a batpack, and run...
PSU sizes: 100W max, integrated into case bottom section
Bays: 1 5.25" Slimline External, 1 2.5" Internal
Slots: 2-3 Mini-PCI (side), 1 Mini-AGP (rear)
Integration: Sound, Network, Graphics (also available as Mini-PCI for first two, Mini-AGP for graphics - some Mini-AGP boards have an extender for TV-out/in on side)
Recommended devices for Mini-PCI and AGP: Sound (MPCI), Network+Modem (MPCI), 802.11 (MPCI), Graphics Card (MAGP).
The desknote isn't atx, but it's what you're looking for. I'd say a thinmini-itx standard would be best. ATX compatible (not in the ports, but who cares?), use Mini-PCI (it'll be in laptops), slimline server/minipc optical, no fdd, 2.5" hdd, sodimms, bottom mount battery (or a AA-based system), a mini-agp standard, LVDS LCD connection
There's LinuxBIOS, a hardware friendly BIOS (spins up drives, etc.), except it's not very complete, BochsBIOS, which isn't hardware friendly, but is fairly complete, and there's a variant of the two that's hardware friendly and fairly complete.
Consumer: "I need to get the recall work done on my car for broken seat belts."
Dealer: "We'll do them for you only if you agree to some terms."
Consumer: "OK, so where are those terms?"
Dealer: (pulls out clipboard) "I can't give them to you, but you do sign right here." (with terms covered up, except for one that says you must agree to all terms to see the other terms)
Consumer: "WTF?!?!? How do I know that there isn't something that says I can't say anything bad about you or you can look in my car whenever the fuck you want?" (drives away, and just as luck would have it, gets into an accident and dies - because the dealer slashed the seatbelts and fucked with the steering system)
IMPORTANT-READ CAREFULLY: This End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for the Microsoft software product identified above, which includes computer software and may include associated media, printed materials, and "online" or electronic documentation ("Product"). An amendment or addendum to this EULA may accompany the Product. YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE PRODUCT. IF YOU DO NOT AGREE, DO NOT INSTALL OR USE THE PRODUCT; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE FOR A FULL REFUND.
1. GRANT OF LICENSE. Microsoft grants you the following rights provided that you comply with all terms and conditions of this EULA:
* Installation and use. You may install, use, access, display and run one copy of the Product on a single computer, such as a workstation, terminal or other device ("Workstation Computer"). A "License Pack" allows you to install, use, access, display and run additional copies of the Product up to the number of "Licensed Copies" specified above. The Product may not be used by more than two (2) processors at any one time on any single Workstation Computer. You may permit a maximum of ten (10) computers or other electronic devices (each a "Device")to connect to the Workstation Computer to utilize the services of the Product solely for file and print services, internet information services, and remote access (including connection sharing and telephony services). The ten connection maximum includes any indirect connections made through "multiplexing" or other software or hardware which pools or aggregates connections. (WTF?!? I've gotten more hits than that on my site in one day!) You may not use the Product to permit any Device to use, access, display or run other executable software residing on the Workstation Computer, nor may you permit any Device to display the Product's user interface, unless the Device has a separate license for the Product. (OH FUCK, VNC IS SCREWED! - but I don't care - this is a pirated copy anyway)
* Storage/Network Use. You may also store or install a copy of the Product on a storage device, such as a network server, used only to install or run the Product on your other Workstation Computers over an internal network; however, you must acquire and dedicate an additional license for each separate Workstation Computer on or from which the Product is installed, used, accessed, displayed or run. A license for the Product may not be shared or used concurrently on different Workstation Computers.
* Reservation of Rights. Microsoft reserves all rights not expressly granted to you in this EULA.
2. UPGRADES. To use a Product identified as an upgrade, you must first be licensed for the product identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the product that formed the basis for your upgrade eligibility.
3. ADDITIONAL SOFTWARE. This EULA applies to updates or supplements to the original Product provided by Microsoft, unless we provide other terms along with the update or supplement.
4. TRANSFER-Internal. You may move the Product to a different Workstation Computer. Transfer to Third Party. The initial user of the Product may make a one-time transfer of the Product to another end user. The transfer has to include all component parts, media, printed materials, this EULA, and if applicable, the Certificate of Authenticity. The transfer may not be an indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the transferred Product must agree to all the EULA terms. No Rental. You may not rent, lease, or lend the Prod
The extra month to develop your own laptop, too? This guy bought a LAPTOP. I know you're talking about desktops, but Dell is pretty well known for their laptops.
RTF/.A. He COULDN'T BOOT LINUX UNLESS HE BOOTED WINDOWS. A previous post said this. If he screwed with the BIOS settings, he would get into windows. He COULD NOT get the warning back, or boot off of a Linux CD.
OK, if that were binding, there would be a power failure or a system crash (I would cause it, of course). I would never have closed the window. I would have wiped it from memory, but I would never had hit Alt-F4, Ctrl-F4, Ctrl-Q, or clicked X, Close (in the context menus), or Close or Exit (both in the file menu)
File and Directory name completion is NOT enabled by default. You can enable or disable file name completion for a particular invocation of CMD.EXE with the/F:ON or/F:OFF switch. You can enable or disable completion for all invocations of CMD.EXE on a machine and/or user logon session by setting either or both of the following REG_DWORD values in the registry using REGEDT32.EXE:
with the hex value of a control character to use for a particular function (e.g. 0x4 is Ctrl-D and 0x6 is Ctrl-F). The user specific settings take precedence over the machine settings. The command line switches take precedence over the registry settings.
If completion is enabled with the/F:ON switch, the two control characters used are Ctrl-D for directory name completion and Ctrl-F for file name completion. To disable a particular completion character in the registry, use the value for space (0x20) as it is not a valid control character.
Completion is invoked when you type either of the two control characters. The completion function takes the path string to the left of the cursor appends a wild card character to it if none is already present and builds up a list of paths that match. It then displays the first matching path. If no paths match, it just beeps and leaves the display alone. Thereafter, repeated pressing of the same control character will cycle through the list of matching paths. Pressing the Shift key with the control character will move through the list backwards. If you edit the line in any way and press the control character again, the saved list of matching paths is discarded and a new one generated. The same occurs if you switch between file and directory name completion. The only difference between the two control characters is the file completion character matches both file and directory names, while the directory completion character only matches directory names. If file completion is used on any of the built in directory commands (CD, MD or RD) then directory completion is assumed.
The completion code deals correctly with file names that contain spaces or other special characters by placing quotes around the matching path. Also, if you back up, then invoke completion from within a line, the text to the right of the cursor at the point completion was invoked is discarded.
OK, so it does add some load to the server, but the MySQL database seems to be working on-and-off under the/.ing, so refreshing may get you in... BTW, at my school, MANY people are that stupid (the getting lost on the way to the printer crap)... and I have to delete the print jobs - on POS inkjets that are overloaded with documents before they get printed 20 times - not counting what the chicks print out multiple times... which usually has a dark background, so I have to replace the ink...
Slashdot Mirror
Did you not see this?
Connect a terminal trough the serial port
The terminal IS THE DISPLAY. For that matter, it could be the keyboard too...
http://www.tldp.org/HOWTO/Modem-HOWTO-16.html
HOWTO on modem doubling (two modems, one ISP). I think your ISP must support it, though.
Hmm, my grandmother gets connections in the 54-56K area (yes, faster than the FCC allows) consistently. Of course, Conexant-based Winmodems didn't work well with my former ISP. The fastest I got normally was 26K! (Of course, when the lines were cleaned in preparation for ADSL, I got a small speed increase) Quick question, though. Does anyone know whether the newer V.92 standard hits 56K upstream? I know it lets you connect to the ISP faster, and offers internet call waiting. Of course, there's also the Emerson Switchboard, which I suspect is a box with 5 V.92 56K modems. I assume you dial in to IT, and then it calls your destination.
Of course, I see more uses than sharing for this. I hope you all remember Blaster. A firewall was a good alternative defense against Blaster (not saying that patching is a bad idea, but you'd probably get all of the patches anyway if you saw how many there were, and over a 56K modem, that's ridculously slow...) AFAIK, this also acts as a firewall. Just think of a cable/dsl modem with a built in router/firewall. Now, take out the cable/dsl modem, and put in a 56K modem. Damn useful, isn't it?
No, it wasn't Daytona. From a Windows Server 2003 history on Paul Thurrott's SuperSite for Windows, here's some info on Daytona:
... well. We did our own. And it just blew them away. Ours was the better Netware client, and customers used ours for years, even after they finally did one. That client enabled the NT desktop, because Netware was the prevalent server in the market. We wouldn't have been able to sell NT desktops otherwise."
The next release, Windows NT 3.5, was code-named Daytona, and shipped in September 1994. "Daytona was a very rewarding project," Thompson said. "We focused on size and performance issues, and on "finishing" many of the first-release features of 3.1. Daytona also had significant functional improvements and enhancements." The original themes for Daytona were size, performance, compression, and Netware compatibility. Two of those goals were emblematic of the time: DoubleSpace-style compression was a hot topic in the early 1990's because disk space was at such a premium, and Netware was the dominant network operating system of the day. "We eventually dropped compression," Thompson said, "but the Netware port was strategic. Novell was ambivalent about the NT desktop ? they didn't know if they wanted to build a client. We offered our assistance, but they kept messing around and
Daytona also benefited from new compiler technology which enabled Microsoft to compress the code size and enable realistic NT desktops on lower-end systems than the original version. "The results were measurable," Thompson said.
Windows NT 3.51 was dubbed the Power PC release, because it was designed around the Power PC version of NT, which was originally supposed to ship in version 3.5. But IBM constantly delayed the Power PC chips, necessitating a separate NT release. "NT 3.51 was a very unrewarding release," Thompson said, contrasting it with Daytona. "After Daytona was completed, we basically sat around for 9 months fixing bugs while we waited for IBM to finish the Power PC hardware. But because of this, NT 3.51 was a solid release, and our customers loved it." NT 3.51 eventually shipped in May 1995.
Wasn't Cairo released in 1996 or something? BTW, I don't think MS wants your money for Cairo anymore. They'd rather have your money for at least Windows 2000, if not XP or Server 2003.
BZZT! It WAS Windows NT 4.0. Here's a FOLDOC entry on NT4:
Windows NT 4
A version of Microsoft's Windows NT operating system, originally code named "Cairo". It was supposed to ship in the first half of 1995. Details are scarce, but it is intended to provide an object-oriented version of Windows.
(1996-07-09)
They do a bad job of cheating. Ever try transparency in Konsole? It's not showing you what's directly behind your Konsole, it's showing you your desktop background.
Hmm, I didn't think anything before Windows 2000 supports alpha-blending. You are talking about Windows NT 4 (code name Cairo), right?
Most AOLusers will be using either AOL's browser or IE4/5/6. TinyURL has a toolbar button. Clicking it in IE4/5/6 will automatically use the URL of the page in question, and copy it to the clipboard in IE4/5/6. Even an AOLuser can figure that out. Unfortunately, it doesn't work in anything that ISN'T IE.
How about we ALL just go to THIS TinyURL? They won't know where these hits are coming from, if other posts in this thread are true.
some things to add:
Mini-itx isn't port layout compatible with most *ATX boards anyway (or, for that matter, other mini-itx boards)...
CardBus should be there...
There should be a keyboard/pointing device standard. Drop a kb/pd combo (toshiba/nec/winbook layout with nipple, for example - my favorite) in, and go. Don't like the kb/pd from your new Dell? Sell it and buy something else...
A widescreen case branch (sub-branches for 15.4" and 17") should exist.
Everything should drop in then be held in by a couple screws. Including the top of the case (4 screws?). Put the mobo, hdd, and cd-rw/dvd (and port card or Mini-PCI/AGP cards) on the tray (which already has a PSU, prewired), screw it down, throw on the top of the case, screw it down, pop on the kb/pd, screw it down, and pop on the LCD and screw it down. If you want, drop the whole thing on a batpack, and run...
Case sizes: 12.1" (for MiniLTX), 14.1", 15" (for LTX), 17" (for WideLTX - NOT widescreen), 15.4" Widescreen (for WideLTX), 17" Widescreen (for MegaWideLTX)
PSU sizes: 100W max, integrated into case bottom section
Bays: 1 5.25" Slimline External, 1 2.5" Internal
Slots: 2-3 Mini-PCI (side), 1 Mini-AGP (rear)
Integration: Sound, Network, Graphics (also available as Mini-PCI for first two, Mini-AGP for graphics - some Mini-AGP boards have an extender for TV-out/in on side)
Recommended devices for Mini-PCI and AGP: Sound (MPCI), Network+Modem (MPCI), 802.11 (MPCI), Graphics Card (MAGP).
Recommended CPUs (using top-of-the-line boards):Intel Pentium 4-M (and Celeron variants), Intel Pentium M, AMD Athlon XP-M
(using outdated boards): Intel Pentium 3-M (and Celeron variants), VIA C3/Eden (Socket 370 only), AMD Athlon-M
Fan size: 1 40-mm case fan on bottom, in right corner, 2 20-mm case fans on back/side
The desknote isn't atx, but it's what you're looking for. I'd say a thinmini-itx standard would be best. ATX compatible (not in the ports, but who cares?), use Mini-PCI (it'll be in laptops), slimline server/minipc optical, no fdd, 2.5" hdd, sodimms, bottom mount battery (or a AA-based system), a mini-agp standard, LVDS LCD connection
There's LinuxBIOS, a hardware friendly BIOS (spins up drives, etc.), except it's not very complete, BochsBIOS, which isn't hardware friendly, but is fairly complete, and there's a variant of the two that's hardware friendly and fairly complete.
No, It's more like this:
Consumer: "I need to get the recall work done on my car for broken seat belts."
Dealer: "We'll do them for you only if you agree to some terms."
Consumer: "OK, so where are those terms?"
Dealer: (pulls out clipboard) "I can't give them to you, but you do sign right here." (with terms covered up, except for one that says you must agree to all terms to see the other terms)
Consumer: "WTF?!?!? How do I know that there isn't something that says I can't say anything bad about you or you can look in my car whenever the fuck you want?" (drives away, and just as luck would have it, gets into an accident and dies - because the dealer slashed the seatbelts and fucked with the steering system)
NOT that this is a legal copy of the OS (unless you count the download of W2K Pro off KaZaA legal), but...
(formatting removed)
Microsoft Windows 2000 Professional Licensed Copies: 1
(formatting removed)
END-USER LICENSE AGREEMENT
(formatting removed)
IMPORTANT-READ CAREFULLY: This End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for the Microsoft software product identified above, which includes computer software and may include associated media, printed materials, and "online" or electronic documentation ("Product"). An amendment or addendum to this EULA may accompany the Product. YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA BY INSTALLING, COPYING, OR OTHERWISE USING THE PRODUCT. IF YOU DO NOT AGREE, DO NOT INSTALL OR USE THE PRODUCT; YOU MAY RETURN IT TO YOUR PLACE OF PURCHASE FOR A FULL REFUND.
1. GRANT OF LICENSE. Microsoft grants you the following rights provided that you comply with all terms and conditions of this EULA:
* Installation and use. You may install, use, access, display and run one copy of the Product on a single computer, such as a workstation, terminal or other device ("Workstation Computer"). A "License Pack" allows you to install, use, access, display and run additional copies of the Product up to the number of "Licensed Copies" specified above. The Product may not be used by more than two (2) processors at any one time on any single Workstation Computer. You may permit a maximum of ten (10) computers or other electronic devices (each a "Device")to connect to the Workstation Computer to utilize the services of the Product solely for file and print services, internet information services, and remote access (including connection sharing and telephony services). The ten connection maximum includes any indirect connections made through "multiplexing" or other software or hardware which pools or aggregates connections. (WTF?!? I've gotten more hits than that on my site in one day!) You may not use the Product to permit any Device to use, access, display or run other executable software residing on the Workstation Computer, nor may you permit any Device to display the Product's user interface, unless the Device has a separate license for the Product. (OH FUCK, VNC IS SCREWED! - but I don't care - this is a pirated copy anyway)
* Storage/Network Use. You may also store or install a copy of the Product on a storage device, such as a network server, used only to install or run the Product on your other Workstation Computers over an internal network; however, you must acquire and dedicate an additional license for each separate Workstation Computer on or from which the Product is installed, used, accessed, displayed or run. A license for the Product may not be shared or used concurrently on different Workstation Computers.
* Reservation of Rights. Microsoft reserves all rights not expressly granted to you in this EULA.
2. UPGRADES. To use a Product identified as an upgrade, you must first be licensed for the product identified by Microsoft as eligible for the upgrade. After upgrading, you may no longer use the product that formed the basis for your upgrade eligibility.
3. ADDITIONAL SOFTWARE. This EULA applies to updates or supplements to the original Product provided by Microsoft, unless we provide other terms along with the update or supplement.
4. TRANSFER-Internal. You may move the Product to a different Workstation Computer. Transfer to Third Party. The initial user of the Product may make a one-time transfer of the Product to another end user. The transfer has to include all component parts, media, printed materials, this EULA, and if applicable, the Certificate of Authenticity. The transfer may not be an indirect transfer, such as a consignment. Prior to the transfer, the end user receiving the transferred Product must agree to all the EULA terms. No Rental. You may not rent, lease, or lend the Prod
The extra month to develop your own laptop, too? This guy bought a LAPTOP. I know you're talking about desktops, but Dell is pretty well known for their laptops.
RTF/.A. He COULDN'T BOOT LINUX UNLESS HE BOOTED WINDOWS. A previous post said this. If he screwed with the BIOS settings, he would get into windows. He COULD NOT get the warning back, or boot off of a Linux CD.
OK, if that were binding, there would be a power failure or a system crash (I would cause it, of course). I would never have closed the window. I would have wiped it from memory, but I would never had hit Alt-F4, Ctrl-F4, Ctrl-Q, or clicked X, Close (in the context menus), or Close or Exit (both in the file menu)
PCI-X is on most Opteron boards. If you want a great example, look at the Tyan Thunder K8W (direct link to a $465.44 board, not the site)
No, both have 8. They can both take 2GB sticks (not what Apple would have you believe - they only sell 1GB sticks).
Really? Here's part of the output from cmd /?:
/F:ON or /F:OFF switch. You can enable or disable
/F:ON switch, the two control
File and Directory name completion is NOT enabled by default. You can
enable or disable file name completion for a particular invocation of
CMD.EXE with the
completion for all invocations of CMD.EXE on a machine and/or user logon
session by setting either or both of the following REG_DWORD values in
the registry using REGEDT32.EXE:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\CompletionChar
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\PathCompletionChar
and/or
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\PathCompletionChar
with the hex value of a control character to use for a particular
function (e.g. 0x4 is Ctrl-D and 0x6 is Ctrl-F). The user specific
settings take precedence over the machine settings. The command line
switches take precedence over the registry settings.
If completion is enabled with the
characters used are Ctrl-D for directory name completion and Ctrl-F for
file name completion. To disable a particular completion character in
the registry, use the value for space (0x20) as it is not a valid
control character.
Completion is invoked when you type either of the two control
characters. The completion function takes the path string to the left
of the cursor appends a wild card character to it if none is already
present and builds up a list of paths that match. It then displays the
first matching path. If no paths match, it just beeps and leaves the
display alone. Thereafter, repeated pressing of the same control
character will cycle through the list of matching paths. Pressing the
Shift key with the control character will move through the list
backwards. If you edit the line in any way and press the control
character again, the saved list of matching paths is discarded and a new
one generated. The same occurs if you switch between file and directory
name completion. The only difference between the two control characters
is the file completion character matches both file and directory names,
while the directory completion character only matches directory names.
If file completion is used on any of the built in directory commands
(CD, MD or RD) then directory completion is assumed.
The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.
OK, so it does add some load to the server, but the MySQL database seems to be working on-and-off under the /.ing, so refreshing may get you in... BTW, at my school, MANY people are that stupid (the getting lost on the way to the printer crap)... and I have to delete the print jobs - on POS inkjets that are overloaded with documents before they get printed 20 times - not counting what the chicks print out multiple times... which usually has a dark background, so I have to replace the ink...
Three words: Check your speedometer...
First link is supposed to be an e-mail link. It's the name of the person who submitted it. Click the second one.