How exactly do employed persons collect unemployment checks? Where do I sign up? This would be a direct and literal interpretation of this comment:
was to ensure that fewer people without jobs were entitled to the benefits
Or did you mean to imply that the "rules" regarding who was eligible for unemployment payments were restructured so as to limit eligibility for those claiming unemployment status. I believe that is what you intended to convey, however, my original query still remains.
One of our clients email is setup so that if you send them an attachment without a particular second attachment, their firewall drops the attachment and only gives you the file. Lemme spell it out for the slow students in the class.
A customer needed an instruction for how to remove the lid from a specialty box. (for field support purposes, the field guys could be morons, so better to have something from the vendor)
He calls me and asks for it, I whip something up in PDF and shoot it over to him.
He calls me and says, got your email but not the attachment. Me: Huh? Him: When I send this email, reply to it and keep the attachment that's there and attach the ddoc again.
So, why is the US Govt not using the same thing? Can it really cost that much to implement (obv not)
You purchased a new copy of windows every other year between 96 and 06 so that's 7 copies but you're only filing for 6. My math comes up to $96 is due you.
Why every two years? Moore's law, of course. New computer, new license.
Businesses are "encouraged" to keep records for at least the past 7 tax/fiscal years. All financially related records.
The company I work for is a small (12 ppl) firm which resells computers with win2k and msofc 2k3. Therefore we truthfully have PoP for probably (say three+) hundreds of copies of each. That's about $45 * 300+ = $13k+? Too bad we're not in Iowa. That's just if we only had 300 PoPs, and I figure it's probably more than that, but I'm being conservative.
Are you aware (as I was not until a few years ago) that it is the law that requires corporations to be obligated to their shareholders. That's it. The whole law. I'm sure it's written in legalese (since I can not remember everything) to the point that it's several books long, but that's the unobfuscated entirety of the foundation of corporate law.
Wouldn't it be nice if corporations were obligated to _society_, since they are just as social organisms as individuals are. Which society I'll leave as a thought experiment to the reader.
So when the flowers get to be about yay'ish high, then the moss starts to sprout, and . . . uh . . .
hrmm, where were we?
Oh yes, the beautiful pubic computer, mostly a single bit binary machine, useful for indicating state. Can commonly be found in the back seats of many cars owned or operated by teenagers after dark, and in locker rooms.
They are also impervious to most liquids, even having been known to thrive in low levels of moisture. The best part is probably the usefulness of being able to use ice (frozen water) for cooling.
I thought it was [move mouse to text] [highlight text] [move mouse to "edit" menu] [select copy] [forget where you are]
And here's another (somewhat, okay, not so much) funny thing, I personally created a test account at work named 'luser' for limited... and nobody else gets it.
But the point of my post was that I agree with you. Isn't that a sad commentary on the training of computer users in general?
How often do you try and "help" people by offering those small tips and they just glare at you and tell you that they don't want to be made more efficient?
GE-FANUC has recently acquired Computer Dynamics who makes a ruggedized product that they call a "Wolverine" which uses a laptop motherboard and has a sunlight-readable display and is encased in an explosion proof case for use in industrial and petroleum situations.
So technically, it's a laptop that you don't have to throw your jacket over your head to see. Although it's not nearly as portable as my HP, and I can't see my HP in direct sunlight, so, yeah, I guess you're right. But if you want a stationary computer that's sunlight readable, the above's your best bet.
Good, haven't met anyone who has seen that movie before I turned them to it.
Wasn't it hella good for being indie? Shame that I hate to talk about it so that others around me don't catch spoilers, but to find out that he had been going around so many times without anybody else knowing . . . took me totally by surprise
But really, what setup are you doing to a VM, thought that was the point of one, I only use 'em for testbeds and never save the changes (or rather, restore from the original install copy) so I can see how things will run in the future
Otherwise, no, no setup on a VM.
Although, with the state of the art rapidly improving, maybe I should consider going to a VM so that I never have to update my "user" o/s again, just keep improving the underlying o/s for hardware sake (cpu, ram and disk)
1. All other commercially available operating systems use flat files to store configuration information. And almost every other operating system out there works better than Windows in a variety of ways, not least of which being performance.
Which requires the flat file to be read again and again, instead of staying in memory constantly, which reduces the disk read time to ascertain values (okay, so it's a memory hog, but in theory using this method reduces the number of disk accesses)
2. Operating systems that use flat files to store configuration information are trivially easy to back up. They're also trivially easy to clone and distribute.
So how often do you anticipate moving ALL your files between two different hardware platforms? Okay, so it's easier to move your files when you have to but I have only changed platforms once in the past 10 years, and that was to go from my desktop to my laptop. at that point, all my programs were out of date, so there was no need to move the image over, although I would have had I felt the need. And by out of date, I mean that I had 5 to 8 year old programs on my desktop when I moved over, so I only took my data directory.
3. People who run operating systems that use flat files tend to READ those flat files. The registry, on the other hand, is so huge and byzantine (again, WHY???) that finding entries in it is like going on a fishing expedition. Nobody really knows what's in their registry. I believe this is by design, not by accident.
I never quite got the hang of reading seventy different flat-files to look for one obscurely named config entry. I also never got the hang of looking in seventy different registry top level entries to look for one obscurely named config entry. so you've got me there. I do, however, routinely know how to identify the elements in my registry, even if I don't know what the individual item may control. And no, I don't know about the undocumented registry keys that when they're not in the registry they don't make a difference but once they get added then you need to know why and you'll usually find that they're documented by that point. can you say any better for the flat file (non-)entries that aren't documented?
4. The registry is IN FACT used to make piracy difficult. Virtually every piece of commercial Windows software stores registration information in the registry, usually in literally dozens of different locations so that to clear out a botched install you have to use a search tool and guess at all the possible names the company may have used for its keys. First, do you think Microsoft isn't doing the same thing??? Second, do you think this isn't by design???
Oh cmon, I can use the windows directory structure to do the same thing, and have you ever asked a noob to look through/etc or/lib for a file without giving them some sort of direction to find it? Granted most o/s's keep their basic directory structure to a minimum, but unless you know the structures intimately, it's always possible to hide through obfuscation or stegano-ing the info. Again, I can use flat files and obfus to make piracy difficult. Not that hard if you stop to think about it.
Now as to multiple locations in the registry, that's fairly "new" for microsoft, as originally everything was kept to a handful of locations, I could even change the registration codes in plain-text until win2k (when they changed to obfusc) but to say that that was the raison-de-etre for the registry? that's just plain uninformed. Not mis-informed, but never-told-at-all.
5. When a hacker creates a Word Macro Virus and the cops catch him like, a week later, how do you think that happens? Word, installed, puts serial number information in the registry and later, into documents. Again, by design.
So now you're stooping to comparing the idiocy of one . . . well, idiot . . . with the design strategy of the re
I agree, and why on earth didn't ms think of adding grep (or even a decent terminal implementation to access the guts of the machine, c'mon, even apple has this)
Also, to state that a windows install may be moved to a new machine by reinstalling, is (to me) the very definition of what we were discussing not happening
Putting the windows installation on a machine with a different hal and not updating the references to that hal in the registry will normally break the image (via the registry) and not allow the image to boot on the new hardware.
A SHILL? by the gods, man, what on earth do you take me for. How do my comments show that I'm a M$ shill, and by what measure did using the registry in windows 95 (the original release, or even back in win3 when there was a registry like mechanism on the computer) prevent people taking the cd to their friends house and installing on that computer, or even making a copy of the floppy disks that they had laying around? yeah, it was expensive at the time, but to prevent piracy? I believe that you misunderstand the concept of theft of intellectual property.
Now it's true that with windows XP or Vista (and previously with office, ad nauseum) that the phone home mechanism of the software, and Microsofts new policies with regards to the windows authentication mechansims, that they are trying to prevent piracy, but in 1995? Pardon me? Yeah right
The registry had two important goals, consolidating configuration information into one location with an easy storage and retrieval method, and application interopability enhancement.
Ya know why CLSID is such a large part of the registry? It has nothing to do with preventing piracy.
Ya know how CurrentControlSet is so thorough, and how it's off on it's own branch of HKLM? Yeah, if you were to replace all of those values with the correct values for the machine that you were moving to (primarily system driver and hardware reference information) then you could in theory just boot windows back up without ever having a glitch. Theory though, not practice. The theory is sound because MS designed the registry to be modular. It's not their fault that other companies don't respect the sandboxing that MS set up, and it's hard for them to enforce that people play nice, but look at the strides they've made via their IDEs (which is where most people write the said crappy software) and.NET v2.
Most of the problems that people have with drivers or program interoperability stem from those two registry branches anyways, is another good reason why all IT folks should be able to recite the major points of the registry, as well as knowing all the places where windows looks when it goes to start the various functions.
This is one of the few shortcomings I can find with the registry, but it's not the fault of MS as a whole, but rather the failure of different groups to consolidate on one storage location for important settings. Then again, two of the reasons why there were so many different locations where settings may have been in the flat files were for security through obfuscation and because sometimes the maximum size you could read on a flat file could have been exceeded due to the number of settings that you might want, so MS designers purposely chose to store info in multiple places, such as the load differences between system.ini and win.ini.
So I've been going in this direction to come back to, the registry didn't have anything to do with limiting piracy, if anything, it's the reason why so many people want to run Windows, even if they don't want to pay for it. The real thing that seems to be annoying to so many geeks is the oobe libs.
The whole point of the registry is to "make piracy difficult". The ONLY reason they created it in the FIRST place was because Bill Gates et al thought their third-rate operating system was so special and important that to protect it from nasty "pirates" they had to essentially lobotomize it. Um, no, not quite
DAP is a great sealant. In fact, many plumbers and others in the small repair business swear by it. I'd say it's probably number 1 amongst those who know of it. Here's two URLs for you:
As a matter of fact, Tim Allen's standup routine (amongst others, I'm sure) references a great bit about DAP and filling the crack revealed when a plumber bends over, but I'll omit that here.
Most people I know of with experience don't even bother to list their A+ certs on their resume anymore. Just for the record, I don't either.
But when you buy a computer from Dell or HP, and you need to add memory, you can't just open the box, or you void the warranty. Again, for the record, I build all of our own boxes at work too.
Except for the whole manufacturers warranty from major manufacturers bit. You know which manufacturers I'm talking about, the guys who developed the CompTIA organization in the first place. It's pretty handy to know that you're not violating a warranty just to open the box and confirm that their field tech needs to come out and replace the motherboard, or the IDE cable*.
So quit bashing having an A+ cert and the bosses who want you to have one. If you don't have one, then it must be because you can't afford the fee to take the exam, so come down to where I live and I'll give you the cash to pay for the exam. Sheesh already.
*Okay, so I would replace my own IDE cable, but still, it's the point of service.
Slashdot Mirror
Or did you mean to imply that the "rules" regarding who was eligible for unemployment payments were restructured so as to limit eligibility for those claiming unemployment status. I believe that is what you intended to convey, however, my original query still remains.
What, its made of Ruby-s?
Or is that what you're expected to pay with?
Que the rupees jokes now
One of our clients email is setup so that if you send them an attachment without a particular second attachment, their firewall drops the attachment and only gives you the file. Lemme spell it out for the slow students in the class.
A customer needed an instruction for how to remove the lid from a specialty box. (for field support purposes, the field guys could be morons, so better to have something from the vendor)
He calls me and asks for it, I whip something up in PDF and shoot it over to him.
He calls me and says, got your email but not the attachment.
Me: Huh?
Him: When I send this email, reply to it and keep the attachment that's there and attach the ddoc again.
So, why is the US Govt not using the same thing? Can it really cost that much to implement (obv not)
You purchased a new copy of windows every other year between 96 and 06 so that's 7 copies but you're only filing for 6. My math comes up to $96 is due you.
Why every two years? Moore's law, of course. New computer, new license.
Businesses are "encouraged" to keep records for at least the past 7 tax/fiscal years. All financially related records.
The company I work for is a small (12 ppl) firm which resells computers with win2k and msofc 2k3. Therefore we truthfully have PoP for probably (say three+) hundreds of copies of each. That's about $45 * 300+ = $13k+? Too bad we're not in Iowa. That's just if we only had 300 PoPs, and I figure it's probably more than that, but I'm being conservative.
Rule: Every post must have at least one AC post a "In Soviet ____ ____s you!1!!1 one"
See the FAQ if you believe me.
And all I need to do is attach actuators to a gyroscope and start pushing it around.
Or how about two smallish black holes contained within strong magnets. I guess those could be considered quite sophisticated gyros, eh?Are you aware (as I was not until a few years ago) that it is the law that requires corporations to be obligated to their shareholders. That's it. The whole law. I'm sure it's written in legalese (since I can not remember everything) to the point that it's several books long, but that's the unobfuscated entirety of the foundation of corporate law.
Wouldn't it be nice if corporations were obligated to _society_, since they are just as social organisms as individuals are. Which society I'll leave as a thought experiment to the reader.
So much of your posts are broken english, it makes me wonder if your market is outside of the US by an oceans width?
My thoughts exactly.
What a silly question, no?
Bird, or is it a bee? I can never remember.
So when the flowers get to be about yay'ish high, then the moss starts to sprout, and . . . uh . . .
hrmm, where were we?
Oh yes, the beautiful pubic computer, mostly a single bit binary machine, useful for indicating state. Can commonly be found in the back seats of many cars owned or operated by teenagers after dark, and in locker rooms.
They are also impervious to most liquids, even having been known to thrive in low levels of moisture. The best part is probably the usefulness of being able to use ice (frozen water) for cooling.
Hope this write-up helps.
And here's another (somewhat, okay, not so much) funny thing, I personally created a test account at work named 'luser' for limited... and nobody else gets it.
But the point of my post was that I agree with you. Isn't that a sad commentary on the training of computer users in general?
How often do you try and "help" people by offering those small tips and they just glare at you and tell you that they don't want to be made more efficient?
GE-FANUC has recently acquired Computer Dynamics who makes a ruggedized product that they call a "Wolverine" which uses a laptop motherboard and has a sunlight-readable display and is encased in an explosion proof case for use in industrial and petroleum situations.
y s.html
http://www.cdynamics.com/
http://www.cdynamics.com/sunlight-readable-displa
So technically, it's a laptop that you don't have to throw your jacket over your head to see. Although it's not nearly as portable as my HP, and I can't see my HP in direct sunlight, so, yeah, I guess you're right. But if you want a stationary computer that's sunlight readable, the above's your best bet.
Good, haven't met anyone who has seen that movie before I turned them to it.
Wasn't it hella good for being indie? Shame that I hate to talk about it so that others around me don't catch spoilers, but to find out that he had been going around so many times without anybody else knowing . . . took me totally by surprise
But really, what setup are you doing to a VM, thought that was the point of one, I only use 'em for testbeds and never save the changes (or rather, restore from the original install copy) so I can see how things will run in the future
Otherwise, no, no setup on a VM.
Although, with the state of the art rapidly improving, maybe I should consider going to a VM so that I never have to update my "user" o/s again, just keep improving the underlying o/s for hardware sake (cpu, ram and disk)
1. All other commercially available operating systems use flat files to store configuration information. And almost every other operating system out there works better than Windows in a variety of ways, not least of which being performance.
Which requires the flat file to be read again and again, instead of staying in memory constantly, which reduces the disk read time to ascertain values (okay, so it's a memory hog, but in theory using this method reduces the number of disk accesses)
2. Operating systems that use flat files to store configuration information are trivially easy to back up. They're also trivially easy to clone and distribute.
So how often do you anticipate moving ALL your files between two different hardware platforms? Okay, so it's easier to move your files when you have to but I have only changed platforms once in the past 10 years, and that was to go from my desktop to my laptop. at that point, all my programs were out of date, so there was no need to move the image over, although I would have had I felt the need. And by out of date, I mean that I had 5 to 8 year old programs on my desktop when I moved over, so I only took my data directory.
3. People who run operating systems that use flat files tend to READ those flat files. The registry, on the other hand, is so huge and byzantine (again, WHY???) that finding entries in it is like going on a fishing expedition. Nobody really knows what's in their registry. I believe this is by design, not by accident.
I never quite got the hang of reading seventy different flat-files to look for one obscurely named config entry. I also never got the hang of looking in seventy different registry top level entries to look for one obscurely named config entry. so you've got me there. I do, however, routinely know how to identify the elements in my registry, even if I don't know what the individual item may control. And no, I don't know about the undocumented registry keys that when they're not in the registry they don't make a difference but once they get added then you need to know why and you'll usually find that they're documented by that point. can you say any better for the flat file (non-)entries that aren't documented?
4. The registry is IN FACT used to make piracy difficult. Virtually every piece of commercial Windows software stores registration information in the registry, usually in literally dozens of different locations so that to clear out a botched install you have to use a search tool and guess at all the possible names the company may have used for its keys. First, do you think Microsoft isn't doing the same thing??? Second, do you think this isn't by design???
Oh cmon, I can use the windows directory structure to do the same thing, and have you ever asked a noob to look through /etc or /lib for a file without giving them some sort of direction to find it? Granted most o/s's keep their basic directory structure to a minimum, but unless you know the structures intimately, it's always possible to hide through obfuscation or stegano-ing the info. Again, I can use flat files and obfus to make piracy difficult. Not that hard if you stop to think about it.
Now as to multiple locations in the registry, that's fairly "new" for microsoft, as originally everything was kept to a handful of locations, I could even change the registration codes in plain-text until win2k (when they changed to obfusc) but to say that that was the raison-de-etre for the registry? that's just plain uninformed. Not mis-informed, but never-told-at-all.
5. When a hacker creates a Word Macro Virus and the cops catch him like, a week later, how do you think that happens? Word, installed, puts serial number information in the registry and later, into documents. Again, by design.
So now you're stooping to comparing the idiocy of one . . . well, idiot . . . with the design strategy of the re
I agree, and why on earth didn't ms think of adding grep (or even a decent terminal implementation to access the guts of the machine, c'mon, even apple has this)
I disagree that my comments were erroneous.
Also, to state that a windows install may be moved to a new machine by reinstalling, is (to me) the very definition of what we were discussing not happening
Putting the windows installation on a machine with a different hal and not updating the references to that hal in the registry will normally break the image (via the registry) and not allow the image to boot on the new hardware.
A SHILL? by the gods, man, what on earth do you take me for. How do my comments show that I'm a M$ shill, and by what measure did using the registry in windows 95 (the original release, or even back in win3 when there was a registry like mechanism on the computer) prevent people taking the cd to their friends house and installing on that computer, or even making a copy of the floppy disks that they had laying around? yeah, it was expensive at the time, but to prevent piracy? I believe that you misunderstand the concept of theft of intellectual property.
Now it's true that with windows XP or Vista (and previously with office, ad nauseum) that the phone home mechanism of the software, and Microsofts new policies with regards to the windows authentication mechansims, that they are trying to prevent piracy, but in 1995? Pardon me? Yeah right
The registry had two important goals, consolidating configuration information into one location with an easy storage and retrieval method, and application interopability enhancement.
.NET v2.
Ya know why CLSID is such a large part of the registry? It has nothing to do with preventing piracy.
Ya know how CurrentControlSet is so thorough, and how it's off on it's own branch of HKLM? Yeah, if you were to replace all of those values with the correct values for the machine that you were moving to (primarily system driver and hardware reference information) then you could in theory just boot windows back up without ever having a glitch. Theory though, not practice. The theory is sound because MS designed the registry to be modular. It's not their fault that other companies don't respect the sandboxing that MS set up, and it's hard for them to enforce that people play nice, but look at the strides they've made via their IDEs (which is where most people write the said crappy software) and
Most of the problems that people have with drivers or program interoperability stem from those two registry branches anyways, is another good reason why all IT folks should be able to recite the major points of the registry, as well as knowing all the places where windows looks when it goes to start the various functions.
This is one of the few shortcomings I can find with the registry, but it's not the fault of MS as a whole, but rather the failure of different groups to consolidate on one storage location for important settings. Then again, two of the reasons why there were so many different locations where settings may have been in the flat files were for security through obfuscation and because sometimes the maximum size you could read on a flat file could have been exceeded due to the number of settings that you might want, so MS designers purposely chose to store info in multiple places, such as the load differences between system.ini and win.ini.
So I've been going in this direction to come back to, the registry didn't have anything to do with limiting piracy, if anything, it's the reason why so many people want to run Windows, even if they don't want to pay for it. The real thing that seems to be annoying to so many geeks is the oobe libs.
Need I go further?
DAP is a great sealant. In fact, many plumbers and others in the small repair business swear by it. I'd say it's probably number 1 amongst those who know of it. Here's two URLs for you:
http://en.wikipedia.org/wiki/DAP
http://www.dap.com/
As a matter of fact, Tim Allen's standup routine (amongst others, I'm sure) references a great bit about DAP and filling the crack revealed when a plumber bends over, but I'll omit that here.
cheers
----
To the mods: Ignore this post
Exactly, 4*250 = 1000 and 250254 thus you should only have to count each finger 250 times to remember where you left off /sarcasm
Most people I know of with experience don't even bother to list their A+ certs on their resume anymore. Just for the record, I don't either.
But when you buy a computer from Dell or HP, and you need to add memory, you can't just open the box, or you void the warranty. Again, for the record, I build all of our own boxes at work too.
But thanks for playing
Except for the whole manufacturers warranty from major manufacturers bit. You know which manufacturers I'm talking about, the guys who developed the CompTIA organization in the first place. It's pretty handy to know that you're not violating a warranty just to open the box and confirm that their field tech needs to come out and replace the motherboard, or the IDE cable*.
So quit bashing having an A+ cert and the bosses who want you to have one. If you don't have one, then it must be because you can't afford the fee to take the exam, so come down to where I live and I'll give you the cash to pay for the exam. Sheesh already.
*Okay, so I would replace my own IDE cable, but still, it's the point of service.