InsideOut's stack is by far the best available, but you can't buy it standalone. You either have to buy one of their Edgeport serial converters or try out the version that Dell has on their FTP Site.
I've also used this one from Bsquare , but it doesn't support Memory Keys, and it's old code.
There are a couple of other ones out there as well.
Funnily enough, when I was recently stuck in Calgary (Go Flames Go!) for an extended period of time, I got so bored at the hotel that I went to Costco and picked up an XBOX pack there, then I got a Hauppage WinTV USB, slapped it together using my Thinkpad and was playing Tetris. I could've tried to break into the hotel's cable link on the in-room TV, but it was a pretty shittly little 20" job and the Thinkpad actually looked better. Pity the Palliser's Ethernet connection didn't support XBOX Live.:-)
Re:DRM will be *needed* by linux
on
Linus on DRM
·
· Score: 1
Do you really want every credit card terminal, ATM and terminal to be Windows because it is the only thing that supports DRM?
Actually, speaking as a person in the ATM industry, there's a great move from OS/2 to Windows (NT, 2000, and/or XP)... but it's mainly due to OS/2 no longer being viable. Diebold, NCR, Wincor Nixdorf, Fujitsu, etc. all have various solutions on Windows they're trying to move customers to.
Someday you will have Linux on ATMs, but it all comes down to what the manufacturer supports and percieves there to be a demand for. No vendor is asking for Linux yet, since their customers haven't been annoyed by the Windows treadmill yet.... When you're amortizing software over a 7+ year life cycle like major banks do, it'll take a while...
Try a manual deletion of your Program Files\mozilla.org directory after the un-install.
I've had a bunch of cases where weird things happen because the un-install routine doesn't wipe out the directory and the install routine doesn't delete it if it exists. You can't layer a new build over each other, so this can cause much weirdness with major code jumps. This seems to happen much more so than in the past.
This won't affect profile data (which is in Documents and Settings by default) unless you manually put them in there. If so, just move 'em out before you delete it and fix your profile as necessary (it's flat text and easy to fix).
If you want to use slightly more stable drivers for the DWL-650, go pull a set from the manufacturer Intersil. I'm using their generic Prism 2.5 drivers with my card (don't know what the 3.0 set does) and they're WAY more stable than the ones on the DLink website. (In my case, the Signal Strength meter actually runs on Win 2K instead of BSOD).
I can only imagine that the XP drivers would be better from them than DLink.
Diebold, NCR, Wincor-Nixdorf, etc. still have a lot of hardware around the world at the various Banks that's deployed running OS/2. Banks also expect to keep their systems running with suported software for many years after a product has been witthdrawn from service (5-10+ years in some cases).
Banks are some of the slowest organizations to switch to new technologies, there is a market for this type of product.
Only now are some of the manufacturers getting to install NT-based systems (Yes, NT - not 2000).
Many of the algos inside of the code are patented by various corporations, so IBM wouldn't be able to give access to them anyways.
USR has patents on the code for x2 connections (which MWave supports), and both they and Lucent have stuff against v.90. Much as people don't like software patents, we've got them and they've got to have the ability to enforce them. It's up to the manufacturer to buy the rights for the use of those techniques.
Rather than going after these DSP executables (which probably wouldn't apply to other DSPs anyways), go after the specific chipset vendors (Lucent et. all) to give out the Linux support.
I wouldn't be suprised if Microsoft still has legal rights involving the Workplace Shell (OS/2's GUI) code and underlying technologies.
There's always been this debate about "open sourcing OS/2" (kernel, drivers, Workplace Shell, etc.), but a couple of things always come up whenever I've heard it discussed:
1) The code is supposedly very messy.
2) It would be EXTREMELY difficult to figure out what could legally be released to outside people. Who's going to pay to do that?
3) If you can't release it all, what use is it to people? What incentive does IBM have to do it, other than "it would be nice?"
BTW, I still continue to use OS/2... my customers still want me to support it.
Slashdot Mirror
You can get USB for NT if you really want it.
InsideOut's stack is by far the best available, but you can't buy it standalone. You either have to buy one of their Edgeport serial converters or try out the version that Dell has on their FTP Site.
I've also used this one from Bsquare , but it doesn't support Memory Keys, and it's old code.
There are a couple of other ones out there as well.
Funnily enough, when I was recently stuck in Calgary (Go Flames Go!) for an extended period of time, I got so bored at the hotel that I went to Costco and picked up an XBOX pack there, then I got a Hauppage WinTV USB, slapped it together using my Thinkpad and was playing Tetris. I could've tried to break into the hotel's cable link on the in-room TV, but it was a pretty shittly little 20" job and the Thinkpad actually looked better. Pity the Palliser's Ethernet connection didn't support XBOX Live. :-)
Do you really want every credit card terminal, ATM and terminal to be Windows because it is the only thing that supports DRM?
Actually, speaking as a person in the ATM industry, there's a great move from OS/2 to Windows (NT, 2000, and/or XP)... but it's mainly due to OS/2 no longer being viable. Diebold, NCR, Wincor Nixdorf, Fujitsu, etc. all have various solutions on Windows they're trying to move customers to.
Someday you will have Linux on ATMs, but it all comes down to what the manufacturer supports and percieves there to be a demand for. No vendor is asking for Linux yet, since their customers haven't been annoyed by the Windows treadmill yet.... When you're amortizing software over a 7+ year life cycle like major banks do, it'll take a while...
Try a manual deletion of your Program Files\mozilla.org directory after the un-install.
I've had a bunch of cases where weird things happen because the un-install routine doesn't wipe out the directory and the install routine doesn't delete it if it exists. You can't layer a new build over each other, so this can cause much weirdness with major code jumps. This seems to happen much more so than in the past.
This won't affect profile data (which is in Documents and Settings by default) unless you manually put them in there. If so, just move 'em out before you delete it and fix your profile as necessary (it's flat text and easy to fix).
If you want to use slightly more stable drivers for the DWL-650, go pull a set from the manufacturer Intersil. I'm using their generic Prism 2.5 drivers with my card (don't know what the 3.0 set does) and they're WAY more stable than the ones on the DLink website. (In my case, the Signal Strength meter actually runs on Win 2K instead of BSOD).
I can only imagine that the XP drivers would be better from them than DLink.
When in doubt, just make up an email addess and let them try.
I pity the poor sucker that's got whatever@fuckoff.net. He's been getting my spam for years.
Diebold, NCR, Wincor-Nixdorf, etc. still have a lot of hardware around the world at the various Banks that's deployed running OS/2. Banks also expect to keep their systems running with suported software for many years after a product has been witthdrawn from service (5-10+ years in some cases).
Banks are some of the slowest organizations to switch to new technologies, there is a market for this type of product.
Only now are some of the manufacturers getting to install NT-based systems (Yes, NT - not 2000).
... and the DSP code will never be.
Many of the algos inside of the code are patented by various corporations, so IBM wouldn't be able to give access to them anyways.
USR has patents on the code for x2 connections (which MWave supports), and both they and Lucent have stuff against v.90. Much as people don't like software patents, we've got them and they've got to have the ability to enforce them. It's up to the manufacturer to buy the rights for the use of those techniques.
Rather than going after these DSP executables (which probably wouldn't apply to other DSPs anyways), go after the specific chipset vendors (Lucent et. all) to give out the Linux support.
I wouldn't be suprised if Microsoft still has legal rights involving the Workplace Shell (OS/2's GUI) code and underlying technologies.
There's always been this debate about "open sourcing OS/2" (kernel, drivers, Workplace Shell, etc.), but a couple of things always come up whenever I've heard it discussed:
1) The code is supposedly very messy.
2) It would be EXTREMELY difficult to figure out what could legally be released to outside people. Who's going to pay to do that?
3) If you can't release it all, what use is it to people? What incentive does IBM have to do it, other than "it would be nice?"
BTW, I still continue to use OS/2... my customers still want me to support it.