Not for Windows since that is bundled with the hardware (#include rant.h). However, when you enter a volume licensing agreement, CDs with all the software you sign up for are sent and updated monthly. Then you order the license and install from the single CDs (or backup copies).
Dos 5 and below used the C> prompt(no directory). Afterwards they changed to C:\>.
No, the parent was correct: the default prompt was driveletter:. The command prompt was used to change it, and there were various system string variables that could be assigned to appear, including $p (path) and $g (greater than sign>. I believe there was also $d (date) and $t (time), and if the ansi.sys terminal driver was loaded you could change colours, use bold and flashing fonts. Some magazines used to hold contests to see who could build funky prompts, as well as batch files to accomplish specific arcane tasks.
Actually, DOS *does* support / but it was made nonfunctional
Actually, MS-DOS supported system calls to get/set the switch character and included a utility called "switchchar" to do just that. Programmers who took the time could check to see the current setting of the switch character and parse arguments accordingly, instead of assuming the "/" was the setting. This would allow the use of "/" in the path.
I don't recall which version introduced this, and apparently it didn't work properly in some versions.
"Back in the days when many of these database were set up, it wasn't possible to store binary data."
That's right, they couldn't afford two values per bit, only one. Hey, wait, what does bit stand for again?
sarcasm
\Sar"casm\, n. [F. sarcasme, L. sarcasmus, Gr. sarkasmo`s, from sarka`zein to tear flesh like dogs, to bite the lips in rage, to speak bitterly, to sneer, fr. sa`rx, sa`rkos, flesh.] A keen, reproachful expression; a satirical remark uttered with some degree of scorn or contempt; a taunt; a gibe; a cutting jest.
You can see what services W2K is running, which is similar to the functionality of msconfig on Win 98. Go to Settings> Control Panel> Administrative Tools> Services. You can right-click on the name of a service to see where it loads from, Stop and Start it manually, and configure the start options.
If there's one piece of software that can make your 2Ghz system perform like a Pentium 200 it's overly aggressive anti-virus software....but I sure don't miss all those "treat your user like a moron" anti-virus packagages.
I use Norton AV software at home, and it, like the Command AV product I use at work, allows the user to configure how "aggressive" it is. Perhaps if you couldn't figure this out you shouldn't have left those packages so quickly...
I would MUCH rather see a species controlled by a long term sterilisation/population reduction process ( 10-20 years to impliment effectively, and long term maintainance ) than this cheap, dangerous and ultimately short-term solution.
Perhaps you aren't in a position to decide: Half a million people in sub-Saharan Africa are estimated to have been infected with sleeping sickness by the tsetse fly and 80 percent of them will likely die, according to the World Health Organization (WHO).
Annual economic losses are put at $4.5 billion.
I suspect if the tsetse fly were causing this type of damage in the US we wouldn't even be having this conversation, since if this were the only effective measure it would have been taken a long time ago. As pointed out, this type of control measure is already in use in the US.
The most important factor is having a ruthless project director. You don't accept slippage, you don't allow mistakes.
However, a good project director understands the project and the time it will take, and doesn't curry favour with management by suggesting impossible time-lines in the first place.
Beware the project director who comes in in mid-stream.
The way that I read this section, it is basically an opt-out provision where you have to actively request in writing that your information not be made available. This is quite different from the situation where the person has to actively agree that the information can be made available. In other words, the default is that the information can be made available in the first case, and not be made available in the second.
The only way this can be considered real protection is if there is a subsequent clause which says that the registered person must be personally notified of the intention to make the information available, and given sufficient time to respond negatively before the information is made available.
Damn! I've sawed off both sides of this VHS tape, stuck them on the side of my BETAMax tape, and now I can't play it in either drive.
Take two aspirin, wait two years, and buy DVD-RAM.
-----
Invent a better mousetrap: someone has the patent for mousetraps, and they'll sue your ass off
Re:Katz writes about things without having 2 clues
on
Selfish Society
·
· Score: 1
Arrogant, yes.
One of the reasons that tech culture seems "selfish" and "arrogant" to others is that the people that run it and work in it have worked HARD to get what they have. Posers, idiots, and other creatures are thrown to the side, because difficult as though it may be to grasp, this culture is a meritocracy. You get what you work for. If you don't know squat, this is easily demonstrable (even by others, to you). This concept is completely foriegn to most people, especially those that have been coddled through life.
No, one of the reasons the tech culture seems "selfish" and "arrogant" to others is that they (the techies) haven't worked hard, they don't need to work hard, and they don't want to work hard. Yes, they work long, but on their own terms. Hard work is forty years in a coal mine or the General Motors assembly line, not being paid for sitting in front of a computer when you'd be doing it for free, just like the script kiddies. People in IT should be thankful for their positions, not arrogant about them.
It is fact that many tech culture workers are selfish and arrogant, and work from the assumption that "Since I know this, and you don't, you are some sort of idiot. That's why you can't get some sort of silly market analysis report out in time. Why do you need to waste my time with this anyway, since I've told you how to do this ten times already?" It ill behooves technology workers to take this attitude unless they are at the pinnacle of their profession, i.e. working for an IPO about to take off (and we know how that market is going). If you are working for a company where you are a cog in the wheel, which would be most of us, you are just that. Currently less dispensable than others, but where will you be in ten years, after every bright kid going into school figures out that the IT industry is where the money is, and suddenly you're mid-thirties, balding, overweight and overpaid? Do you think every one of you that currently mouths off about the "suits" is going to survive that shitstorm? That dweeb in accounting you humiliated by suggesting they use an abacus is suddenly the CFO. Whoops.
I must admit that much of my regular work is involved with administrative chores now, and not technical work (yes, I am somewhat suitish). However, I am now supervising and involved with hiring staff for technical positions, and our organization tries to weed out candidates who consider their work superior to the delivery of the product (and our written and interview questions are designed in part to determine that). Certainly there is no room for a person who doesn't have the technical skills, but when dealing with clients interpersonal skills are valuable. It doesn't matter how good the support is technically, if the client can't get the job done with that support, and it doesn't matter if the client thinks a mouse is a foot pedal, the fault is with the support.
The best example I can think of, of this foolish "geekish" pride, is from an askSlashdot submission a month or so ago. A submitter was considering writing a Windows front end to a text configuration file, for what software I can't recall. The question was whether or not this would be a legitimate thing to do, considering that maybe every user of the software should have to pay their dues and learn how to edit text files. Now, that is a bit arrogant in itself. The kicker is that the submitter was willing to write the front end in Visual Basic.
Now, I don't know how long you folks have been around. I've been around long enough to appreciate the message about the dumbing down of programming in: http://www.salon.com/21st/feature/1998/05/cov_12fe ature.html , and the error message about ROM BASIC. The first PCs I worked on actually would boot BASIC, but I worked on several microcomputers before that that ran under the CPM OS. Yes, I used the early versions of MS Basic, and also the early versions of C for the PC - Lattice had the best one, and MS was an also-ran until about 1989, then Lattice folded. I used a text editor to write Basic, C, Clipper 87, C++, and Clipper 5 software in commercial versions, and used punch cards to write assembly language programs for an IBM 360 when I was going to university. The cards for a primitive encryption scheme were laboriously entered on a card printer, and for the encryption program were about two feet high.
Now let me ask, regarding this Visual Basic pinhead and his ilk, do you think that your mighty knowledge of creating a form and dragging text fields on to it entitles you to suggest that you are so far advanced of someone? If you were dropped on a desert island with a text editor and a basic compiler what would you do? Sorry, rub all the bottles you want, there ain't no wizards here. You have six months to produce a program to get you off the island. See ya.
Somewhat anxious about the attitude? Perhaps. I do think there will be a somewhat startling movement in the IT labour force as new graduates come on board who are better qualified and more knowledgeable than those who have been there by virtue of experience, and that means a window of about 10 years that started a few years ago. If you don't expect to be where you are right now in 10 years time, you have to question where you will be in 5 years time, and two years time, and start to settle down. I have two people on my staff who worked for a three-initial mainframe company, that thought it would never end, and one who worked on copiers for a late-alphabet company that didn't think it would end either.
The only thing that doesn't work, is the arrogance. You can be selfish all you want, but you have to treat the client as number one.
Slashdot Mirror
There is - that is what the Trusted Sites and Restricted Sites options are for.
Not for Windows since that is bundled with the hardware (#include rant.h). However, when you enter a volume licensing agreement, CDs with all the software you sign up for are sent and updated monthly. Then you order the license and install from the single CDs (or backup copies).
No, the parent was correct: the default prompt was driveletter:. The command prompt was used to change it, and there were various system string variables that could be assigned to appear, including $p (path) and $g (greater than sign>. I believe there was also $d (date) and $t (time), and if the ansi.sys terminal driver was loaded you could change colours, use bold and flashing fonts. Some magazines used to hold contests to see who could build funky prompts, as well as batch files to accomplish specific arcane tasks.
Actually, MS-DOS supported system calls to get/set the switch character and included a utility called "switchchar" to do just that. Programmers who took the time could check to see the current setting of the switch character and parse arguments accordingly, instead of assuming the "/" was the setting. This would allow the use of "/" in the path.
I don't recall which version introduced this, and apparently it didn't work properly in some versions.
Gosh, when I die I hope to go to a place where the OS has a GUI.
...even the ./ moderation system isn't perfect.
"Back in the days when many of these database were set up, it wasn't possible to store binary data." That's right, they couldn't afford two values per bit, only one. Hey, wait, what does bit stand for again?
Ironically, it does not. Try Small Computer System Interface. Or, in early days System Can't See It.
sarcasm \Sar"casm\, n. [F. sarcasme, L. sarcasmus, Gr. sarkasmo`s, from sarka`zein to tear flesh like dogs, to bite the lips in rage, to speak bitterly, to sneer, fr. sa`rx, sa`rkos, flesh.] A keen, reproachful expression; a satirical remark uttered with some degree of scorn or contempt; a taunt; a gibe; a cutting jest.
You can see what services W2K is running, which is similar to the functionality of msconfig on Win 98. Go to Settings> Control Panel> Administrative Tools> Services. You can right-click on the name of a service to see where it loads from, Stop and Start it manually, and configure the start options.
ripped straight out of our reporter's handbook:
...if [we choose] to run stories from our wire service, we are completely liable for the content of those stores--even though we didn't right them.
There you have it, straight from the horse's mouth. Reading that for the first time really shocked me.
It really shocked me too - speaking of shoddy reporting, who does your proofreading?
You just haven't looked hard enough. There's an alt newsgroup about free newsservers (hint, hint) that you might want to investigate.
The poor guy can't read alt.* groups, so you tell him to read an alt newsgroup...
I use Norton AV software at home, and it, like the Command AV product I use at work, allows the user to configure how "aggressive" it is. Perhaps if you couldn't figure this out you shouldn't have left those packages so quickly...
Perhaps you aren't in a position to decide:
Half a million people in sub-Saharan Africa are estimated to have been infected with sleeping sickness by the tsetse fly and 80 percent of them will likely die, according to the World Health Organization (WHO).
Annual economic losses are put at $4.5 billion.
I suspect if the tsetse fly were causing this type of damage in the US we wouldn't even be having this conversation, since if this were the only effective measure it would have been taken a long time ago. As pointed out, this type of control measure is already in use in the US.
Of SPAM would this produce? As if regular spam weren't bad enough.
FWIW, Novell also offers free downloads of LDAP libraries for C and Java although you might have to register for their Developer program.
Access from: developer.novell.com
The most important factor is having a ruthless project director. You don't accept slippage, you don't allow mistakes.
However, a good project director understands the project and the time it will take, and doesn't curry favour with management by suggesting impossible time-lines in the first place.
Beware the project director who comes in in mid-stream.
Duncan (not the MacBeth one)
The way that I read this section, it is basically an opt-out provision where you have to actively request in writing that your information not be made available. This is quite different from the situation where the person has to actively agree that the information can be made available. In other words, the default is that the information can be made available in the first case, and not be made available in the second.
The only way this can be considered real protection is if there is a subsequent clause which says that the registered person must be personally notified of the intention to make the information available, and given sufficient time to respond negatively before the information is made available.
I believe a proposal for a technical solution would be slightly more complicated, and involve...
Smoke AND Mirrors.
Winbatch (http://www.winbatch.com) isn't free, but isn't very expensive either.
Actually, I'd ask what you were drinking, and see if I might have one.
Damn! I've sawed off both sides of this VHS tape, stuck them on the side of my BETAMax tape, and now I can't play it in either drive. Take two aspirin, wait two years, and buy DVD-RAM. ----- Invent a better mousetrap: someone has the patent for mousetraps, and they'll sue your ass off
No, one of the reasons the tech culture seems "selfish" and "arrogant" to others is that they (the techies) haven't worked hard, they don't need to work hard, and they don't want to work hard. Yes, they work long, but on their own terms. Hard work is forty years in a coal mine or the General Motors assembly line, not being paid for sitting in front of a computer when you'd be doing it for free, just like the script kiddies. People in IT should be thankful for their positions, not arrogant about them.
It is fact that many tech culture workers are selfish and arrogant, and work from the assumption that "Since I know this, and you don't, you are some sort of idiot. That's why you can't get some sort of silly market analysis report out in time. Why do you need to waste my time with this anyway, since I've told you how to do this ten times already?" It ill behooves technology workers to take this attitude unless they are at the pinnacle of their profession, i.e. working for an IPO about to take off (and we know how that market is going). If you are working for a company where you are a cog in the wheel, which would be most of us, you are just that. Currently less dispensable than others, but where will you be in ten years, after every bright kid going into school figures out that the IT industry is where the money is, and suddenly you're mid-thirties, balding, overweight and overpaid? Do you think every one of you that currently mouths off about the "suits" is going to survive that shitstorm? That dweeb in accounting you humiliated by suggesting they use an abacus is suddenly the CFO. Whoops.
I must admit that much of my regular work is involved with administrative chores now, and not technical work (yes, I am somewhat suitish). However, I am now supervising and involved with hiring staff for technical positions, and our organization tries to weed out candidates who consider their work superior to the delivery of the product (and our written and interview questions are designed in part to determine that). Certainly there is no room for a person who doesn't have the technical skills, but when dealing with clients interpersonal skills are valuable. It doesn't matter how good the support is technically, if the client can't get the job done with that support, and it doesn't matter if the client thinks a mouse is a foot pedal, the fault is with the support.
The best example I can think of, of this foolish "geekish" pride, is from an askSlashdot submission a month or so ago. A submitter was considering writing a Windows front end to a text configuration file, for what software I can't recall. The question was whether or not this would be a legitimate thing to do, considering that maybe every user of the software should have to pay their dues and learn how to edit text files. Now, that is a bit arrogant in itself. The kicker is that the submitter was willing to write the front end in Visual Basic.
Now, I don't know how long you folks have been around. I've been around long enough to appreciate the message about the dumbing down of programming in: http://www.salon.com/21st/feature/1998/05/cov_12fe ature.html , and the error message about ROM BASIC. The first PCs I worked on actually would boot BASIC, but I worked on several microcomputers before that that ran under the CPM OS. Yes, I used the early versions of MS Basic, and also the early versions of C for the PC - Lattice had the best one, and MS was an also-ran until about 1989, then Lattice folded. I used a text editor to write Basic, C, Clipper 87, C++, and Clipper 5 software in commercial versions, and used punch cards to write assembly language programs for an IBM 360 when I was going to university. The cards for a primitive encryption scheme were laboriously entered on a card printer, and for the encryption program were about two feet high.
Now let me ask, regarding this Visual Basic pinhead and his ilk, do you think that your mighty knowledge of creating a form and dragging text fields on to it entitles you to suggest that you are so far advanced of someone? If you were dropped on a desert island with a text editor and a basic compiler what would you do? Sorry, rub all the bottles you want, there ain't no wizards here. You have six months to produce a program to get you off the island. See ya.
Somewhat anxious about the attitude? Perhaps. I do think there will be a somewhat startling movement in the IT labour force as new graduates come on board who are better qualified and more knowledgeable than those who have been there by virtue of experience, and that means a window of about 10 years that started a few years ago. If you don't expect to be where you are right now in 10 years time, you have to question where you will be in 5 years time, and two years time, and start to settle down. I have two people on my staff who worked for a three-initial mainframe company, that thought it would never end, and one who worked on copiers for a late-alphabet company that didn't think it would end either.
The only thing that doesn't work, is the arrogance. You can be selfish all you want, but you have to treat the client as number one.