Bust-a-move is at least circa '91 or '92, and that was for the US NeoGeo version of it. I'm sure the Japanese version was around much earlier, and even then it may have been ported to the NG from something else, as it really isn't too hardware intensive.
"Even more annoying is management usually falls for it."
This is the main reason why many people do get these certifications. I know that's why I got mine...not because I wanted to brag about it, but because I wanted a raise. Conversation went something like this:
Me: More money please.
PHB: Got MCSE?
Me: No, will it get me mo' money?
PHB: Yes.
Me: Done.
Let's be real, if it will get you a job or a raise, most people will do it, even if you're bored stupid with the course/study material.
A: For streaming content from the Internet; the standard HTTP port 80 is used, so make sure that this port is open for outgoing traffic
OK, I know what they really mean, (ie, request goes out port 80, streaming media back in another established port connection) but if you read this quickly, it almost sounds like they're sending some data out from this device. Perhaps they are. Spyware anyone?
I don't know about one way polarization, but you might be able to pass a given wavelength of light in through a filter, absorb the energy somehow and then re-radiate it out at a different wavelength that the filter does not let back out. This is similar to how a greenhouse works, but the re-radiated light's wavelength would have to stay in the range that the cells can absorb. As IANAP, I really don't know if that is possible or even the best way to do it. In short, I'm pulling it from my ass, but it could be possible.
"due to scripts still being able to act as admin and thus still capable of raising hell"
Well, anything you let run as admin will give you hell...and then some. Granted, you can't exercise much control over the privilege levels that a script runs under on Win9x/ME, but in the context of NT/2K/XP, an admin that lets anything run under admin priviliges is just asking for trouble. By that argument, any *nix program that has to run as root (I suppose while not in a chroot jail or something similar) is theoretically susceptible to the same troubles. Now obviously any scripting that is to be useful to a sysadmin must be run at some higher privilege level, otherwise it probably couldn't do anything too useful. But that kind of scripting is typically run in the log in, run script, log out kind of fashion.
The scripts that cause nightmares are those that happen to run on an unsecured system, either simply poorly configured or not patched, or running in the context of a user that happens to have privileges. In any case, this can happen in *nix system as well, it just typically doesn't because most people don't log in as root all day long whereas the typical home user with 2K/XP is ALWAYS logging in as admin, since that's the default.
I guess my point is that scripting on windows shouldn't be any more of a security issue as scripting on a *nix system. It all depends on the context the script is run in. Secure a system (and more importantly, user privileges), and you won't have a problem.
I'll give you that scripting in Windows has caused a ton of problems...trust me, I'm a Windows admin (for better or worse:) )and I've had to fix a good many of the things that scripting worms have fubarred! But it wasn't the scripting that caused the problem...poorly written applications that let scripts run loose cause the problem. Which goes back to what I was saying, if you configure the systems correctly (and keep-up with the neverending patches), scripting isn't a problem, security wise.
I'm obviously missing your point...how does scriptability cause a problem? If you are referring to viruses or something like that, a properly configured system will go a long way towards preventing that.
As far as looseness of the implementation...I think the scripting implementation in Windows is far tighter than anything in the *nix world, save for maybe PERL, which is also available for windows of course. Now don't get me wrong, scripting windows can be downright arcane at times, but most people who RTFM won't have any problems.
Yeah, when I read the parent post, I was thinking the same thing...that he has no idea what he's talking about. There is an article on MS's site that actually RECOMMENDS pulling the plug in those situations where the computer won't shut down properly.
The only time I've EVER seen NTFS lose data was on an NT 4 workstation that was improperly configured. Someone had initially installed NT on the machine with a single partition occupying the whole of a 4 GB drive. Well, somewhere down the road, the drive was upgraded and the existing drive was cloned to an 8 GB drive. All seemed to work well until one day machine STOP ERRORS on boot. Why?... well, after investigation...it seems that NT can't find the boot files past 7.something gig and apparently the offending file somehow got move past that limit. Actually, I guess this didn't even lose the data, just NT 4 couldn't find it anymore when trying to boot from that drive. Boot from another drive, and all the files were there.
If we were strictly speaking about Linux based servers vs. Windows based servers, I'd consider that Linux would be cheaper in the long run. Bring some desktops into the mix though, and I say no way. Things like group policy, remote software installation, and RIS make supporting Windows clients super easy. Linux tools have much to gain in this arena. And, despite many contrary claims here on slashdot, windows IS completely scriptable.
PERL is absolutely not necessary for managing users or groups (or just about anything else for that matter in Win2K). Read up on WSH, ADSI, and LDAP, and you'll have just about everything you need to know in order to script EVERYTHING in a Windows environment.
For example, I work for a small community college that stores/processes all of its student data on an HP3000 running MPE/ix. I managed to get my Win2K domain controllers to automagically create/delete user accounts, groups, and even Exchange 2000 mailboxes, based on what the HP3000 had for registered or dropped students. If you want some examples of this, just go to the MS scripting center.
Damn, you're right about Mr. Pibb, but I'm pretty sure Dr. P isn't found with Pepsi products. Anyone know if it was ever distributed or bottled by Coke?
Oops, forgot to mention that this was in response to the "prior art" link in the original post. Also, I meant gets, not get's, for all you grammar freaks.
Finger just get's a user's info. Talk was what we always used for 2 way chatting. Also, which came first...MS's crappy MSchat in early versions of windows, or AIM?
TTY is great and all, but since this was promoted as a cell-phone app, I find it very hard to believe that anyone would even attempt to teletype on a cell phone or pda for that matter.
Sure, they'll be able to "hear" you, but how will you hear them? Seems like this company has only half the equation here. Also, not that I'm a lip reader, but those demos were very erratic for me to lip read.
Note that I've never had direct experience with this, but I've heard in several different places that yes, you can just connect the ethernet port to your nic in any given OS and it'll work; however, these same people also said that without running the special software that your transfer rates suffer tremendously.
And this could be way out there, but if the stuff reacts with air, couldn't you just spray the surface with some optically clear but non-air permeable gunk? This of course assumes said gunk exists, but I'm sure it does.
I work for a an agency of NYS. About a month ago, we received a state-wide bulletin requesting information on failure rates of hard drives. The bulletin stated that there had been a huge increase in drive failures in state-owned computers since 1st qtr 2002, but that it wasn't limited to a single vendor. All of the major manufacturers apparently put out crap. In any case, my agency had observed almost exactly the same failure rate as the rest of the state agencies on the whole, so I tend to believe that manufacturers are just plain making garbage these days. Just my $.02
All of our union contracts, college bylaws, yadda yadda have been converted to PDF - mind you, from A PRINTED COPY no less, not the original word-processed documents that were ALREADY ON DISK.
We were actually awarded a paperless office grant and the whole project was centered around Acrobat/Messenger/Capture. They might as well have called the grant the Adobe Gov't Subsidy Program. I mean, please, if you want to do it paperless, do it right by sticking the raw data/text in a database somewhere and formatting it only on demand or on the fly when it is needed.
99 bucks for already out of date software.
on
Xandros 1.0
·
· Score: 0, Redundant
No thanks.
A good product, actually
on
Airborne Mouse
·
· Score: 5, Informative
We've been using the Gyromouse Pro from these guys for a while now. It works great and the recharging base is a plus. The only difference I can see from what we use and the new one is that the new one is optical when you use it on the desk, whereas the gyro pro still uses old ball technology.
Slashdot Mirror
Bust-a-move is at least circa '91 or '92, and that was for the US NeoGeo version of it. I'm sure the Japanese version was around much earlier, and even then it may have been ported to the NG from something else, as it really isn't too hardware intensive.
otherwise known as puzzle bobble to the rest of the world. Both mame and NeoRageX play it very well, btw. :)
"Even more annoying is management usually falls for it."
This is the main reason why many people do get these certifications. I know that's why I got mine...not because I wanted to brag about it, but because I wanted a raise. Conversation went something like this:
Me: More money please.
PHB: Got MCSE?
Me: No, will it get me mo' money?
PHB: Yes.
Me: Done.
Let's be real, if it will get you a job or a raise, most people will do it, even if you're bored stupid with the course/study material.
A: For streaming content from the Internet; the standard HTTP port 80 is used, so make sure that this port is open for outgoing traffic
OK, I know what they really mean, (ie, request goes out port 80, streaming media back in another established port connection) but if you read this quickly, it almost sounds like they're sending some data out from this device. Perhaps they are. Spyware anyone?
I don't know about one way polarization, but you might be able to pass a given wavelength of light in through a filter, absorb the energy somehow and then re-radiate it out at a different wavelength that the filter does not let back out. This is similar to how a greenhouse works, but the re-radiated light's wavelength would have to stay in the range that the cells can absorb. As IANAP, I really don't know if that is possible or even the best way to do it. In short, I'm pulling it from my ass, but it could be possible.
"due to scripts still being able to act as admin and thus still capable of raising hell"
Well, anything you let run as admin will give you hell...and then some. Granted, you can't exercise much control over the privilege levels that a script runs under on Win9x/ME, but in the context of NT/2K/XP, an admin that lets anything run under admin priviliges is just asking for trouble. By that argument, any *nix program that has to run as root (I suppose while not in a chroot jail or something similar) is theoretically susceptible to the same troubles. Now obviously any scripting that is to be useful to a sysadmin must be run at some higher privilege level, otherwise it probably couldn't do anything too useful. But that kind of scripting is typically run in the log in, run script, log out kind of fashion.
The scripts that cause nightmares are those that happen to run on an unsecured system, either simply poorly configured or not patched, or running in the context of a user that happens to have privileges. In any case, this can happen in *nix system as well, it just typically doesn't because most people don't log in as root all day long whereas the typical home user with 2K/XP is ALWAYS logging in as admin, since that's the default.
I guess my point is that scripting on windows shouldn't be any more of a security issue as scripting on a *nix system. It all depends on the context the script is run in. Secure a system (and more importantly, user privileges), and you won't have a problem.
I'll give you that scripting in Windows has caused a ton of problems...trust me, I'm a Windows admin (for better or worse :) )and I've had to fix a good many of the things that scripting worms have fubarred! But it wasn't the scripting that caused the problem...poorly written applications that let scripts run loose cause the problem. Which goes back to what I was saying, if you configure the systems correctly (and keep-up with the neverending patches), scripting isn't a problem, security wise.
I'm obviously missing your point...how does scriptability cause a problem? If you are referring to viruses or something like that, a properly configured system will go a long way towards preventing that.
As far as looseness of the implementation...I think the scripting implementation in Windows is far tighter than anything in the *nix world, save for maybe PERL, which is also available for windows of course. Now don't get me wrong, scripting windows can be downright arcane at times, but most people who RTFM won't have any problems.
Yeah, when I read the parent post, I was thinking the same thing...that he has no idea what he's talking about. There is an article on MS's site that actually RECOMMENDS pulling the plug in those situations where the computer won't shut down properly.
The only time I've EVER seen NTFS lose data was on an NT 4 workstation that was improperly configured. Someone had initially installed NT on the machine with a single partition occupying the whole of a 4 GB drive. Well, somewhere down the road, the drive was upgraded and the existing drive was cloned to an 8 GB drive. All seemed to work well until one day machine STOP ERRORS on boot. Why?... well, after investigation...it seems that NT can't find the boot files past 7.something gig and apparently the offending file somehow got move past that limit. Actually, I guess this didn't even lose the data, just NT 4 couldn't find it anymore when trying to boot from that drive. Boot from another drive, and all the files were there.
If we were strictly speaking about Linux based servers vs. Windows based servers, I'd consider that Linux would be cheaper in the long run. Bring some desktops into the mix though, and I say no way. Things like group policy, remote software installation, and RIS make supporting Windows clients super easy. Linux tools have much to gain in this arena. And, despite many contrary claims here on slashdot, windows IS completely scriptable.
PERL is absolutely not necessary for managing users or groups (or just about anything else for that matter in Win2K). Read up on WSH, ADSI, and LDAP, and you'll have just about everything you need to know in order to script EVERYTHING in a Windows environment.
For example, I work for a small community college that stores/processes all of its student data on an HP3000 running MPE/ix. I managed to get my Win2K domain controllers to automagically create/delete user accounts, groups, and even Exchange 2000 mailboxes, based on what the HP3000 had for registered or dropped students. If you want some examples of this, just go to the MS scripting center.
Damn, you're right about Mr. Pibb, but I'm pretty sure Dr. P isn't found with Pepsi products. Anyone know if it was ever distributed or bottled by Coke?
..if Pepsi only actually made Dr. Pepper. Last I checked, it was a Coke product. Perhaps a brain-fart you had?
Oops, forgot to mention that this was in response to the "prior art" link in the original post. Also, I meant gets, not get's, for all you grammar freaks.
Finger just get's a user's info. Talk was what we always used for 2 way chatting. Also, which came first...MS's crappy MSchat in early versions of windows, or AIM?
TTY is great and all, but since this was promoted as a cell-phone app, I find it very hard to believe that anyone would even attempt to teletype on a cell phone or pda for that matter.
Sure, they'll be able to "hear" you, but how will you hear them? Seems like this company has only half the equation here. Also, not that I'm a lip reader, but those demos were very erratic for me to lip read.
Note that I've never had direct experience with this, but I've heard in several different places that yes, you can just connect the ethernet port to your nic in any given OS and it'll work; however, these same people also said that without running the special software that your transfer rates suffer tremendously.
Just what I've heard.
Microsoft: We'll break your apps!
App developers: And just exactly how is this different from Windows as it stands now?
And this could be way out there, but if the stuff reacts with air, couldn't you just spray the surface with some optically clear but non-air permeable gunk? This of course assumes said gunk exists, but I'm sure it does.
I work for a an agency of NYS. About a month ago, we received a state-wide bulletin requesting information on failure rates of hard drives. The bulletin stated that there had been a huge increase in drive failures in state-owned computers since 1st qtr 2002, but that it wasn't limited to a single vendor. All of the major manufacturers apparently put out crap. In any case, my agency had observed almost exactly the same failure rate as the rest of the state agencies on the whole, so I tend to believe that manufacturers are just plain making garbage these days. Just my $.02
All of our union contracts, college bylaws, yadda yadda have been converted to PDF - mind you, from A PRINTED COPY no less, not the original word-processed documents that were ALREADY ON DISK.
We were actually awarded a paperless office grant and the whole project was centered around Acrobat/Messenger/Capture. They might as well have called the grant the Adobe Gov't Subsidy Program. I mean, please, if you want to do it paperless, do it right by sticking the raw data/text in a database somewhere and formatting it only on demand or on the fly when it is needed.
No thanks.
We've been using the Gyromouse Pro from these guys for a while now. It works great and the recharging base is a plus. The only difference I can see from what we use and the new one is that the new one is optical when you use it on the desk, whereas the gyro pro still uses old ball technology.
Personally I prefer a non-crappy network card. 3Com, Dlink, etc.
And you think either of these 2 aren't crappy? I'll give you, 3Com is borderline non-crappy, but Dlink is horrible.