About 2 months ago a very anti-technology professor of mine pointed out that the reason the matrix is popular is because it tells nerds what they want to hear, that they can still be cool and powerful even if where they are right now is a small room, by themselves, spending 14 hours a day stairing at a computer screen.
I'll have to do that. I just wanted to add EQIM since I run that some. Wasn't a big deal though since I have an icon for it on my desktop already.
WineX3 has been good to me
on
WineX 3.0 Examined
·
· Score: 4, Insightful
I subscribe and wineX3 has been supprisingly good. It's running the games I am really interested in. I'm back to playing Everquest (maybe not a good thing), Warcraft3, Jedi Knight 2, and Baulder's Gate 2. I'm also using EQIM with it. All of these work basically transparently. There's of course the overhead and minor things, (names over character heads are not very legible in everquest though I hear cvs fixes this), but really it doesn't bother me one bit and I don't have to boot out to windows to play these games.
Point2Play basically acts kind of like a registry for windows games. Not exactly what it does but a reasonable analogy. I wish you could add directories/executables directly to it rather than having to do an install, but other than that it's working well as a launch point for my windows games.
Over all I am pleased with wineX3. I thought the wineX3 preview was lacking but this version seams acceptable.
Electrical Engineer. Anyway, if you look at the fingerworks equipment, it combines typing with gestures. Also, though I don't have the link, there have been people who have worked on gloves which track hands to determine what their typing, (I assume by position and velocity). Typing could easily be included in anything capable of 3D gestures without a physical device to type on.
I honestly think people just like keyboards. They work for 1 job rather well, english text input. Because of that people are rather unwilling to admit that they might have faults. But for input of anything else, they don't, (we had to develop the mouse to make up for this). The mouse isn't optimal though. It requires moving our hands to it to use and is only capapble of recording very basic gestures.
There is also of course the fact that many people don't like the idea of moving to a new input medium. There is definately a burrier to overcome in that respect, but it doesn't exist with youths who, if taught to use a 2D or 3D aparatus capable of gesture recognition, would be able to use it to it's full capability with out an unnecessary initial investment of learning.
The problem is not that there is a flaw in keyboards per-say, but that the input interface must change from pushing buttons. I see the progression of input as the current button to gestures to direct input, (ie, electric signals transmitted directly to the computer either through an implant or sensors attached to the body).
Right now we have reached the beginning of the transition away from button inputs to gesture inputs. There are of course many projects working on gesture inputs. The first that are really viable are the 2D ones from fingerworks.com. The next will be refined versions of the P5 Glove or the sensible phantom. I think eventually gesture based input will be the type used in Minority Report, (see the 1st and 10th images in the gallery).
Finally, I think we will move on to direct input. It's been shown that people can control very simple objects, (move a ball to the top or bottom of the screen), with electrodes connected to their head. Unfortunately so far it has not been responsive enough to see application. Input may also be of the form in Ghost in the Shell where people have wireless connections through implants in their body and also physical jacks in the back of their neck. (Another thing shown in the movie are fingers that come apart on wires to type. Rather than that I'd expect a low-power data transmission in the fingers so set the fingers in appropriately shaped cavities and have the data transmitted across the skin.)
Keyboards are nice. They have worked for a long time, but it is time to replace them. Slowly we can transition from keyboards, through the 2D gesture inputs of fingerworks to 3D inputs along the lines of minority report at which time, hopefully, direct input methods will be viable.
I've posted this before but since people still seem to have problems with quicktime and linux I'll post it again w/ a bit more added on.
As everyone should be aware, mplayer playes quicktime movies on linux. Unfortunately, alot of people have problems with the audio. Basically, the problem is that the new quicktime movies use aac (advanced audio codec) audio instead of mp3 like older quicktime files. The solution of course is to install aac support for mplayer.
To do this, first you must install the codec. The codec that supports aac is available at audiocoding.com. It's called FAAD2. I used the cvs (1.2 beta) so I don't know if the stable 1.1 will work. (The 1.1 requires a small patch to get it to compile with newer forms of the libsndfile or forms of gcc > 3.) Other than that it compiled fine. The second change is that the libraries for faad are installed in/usr/local/lib. Apperently mplayer doesn't, by default, look in/usr/local/lib. I symbolically linked the libraries to/usr/lib (where mplayer DOES look), but I assume you could add/usr/local/lib to the search path.
Hopefully this helps many of the people who want to run these and other quicktime files on linux. Mplayer has made great strides and while it's not perfect, (crashes if you try to run 2 qt files back to back without restarting), it is the best there is for linux, (or for that matter any other system). (As an alternate note, the rpm faad2-1.1-fr1.20030409.i386.rpm does not work. While it installs to the correct place, the mplayer config is not able to detect the version of faad from it. I've heard that it will work as long as you also install the devel package, but did not test it.)
Now, it turns out that it's pretty easy to embed mplayer into mozilla, (or in my case phoen...err, firebird). You just need to go to the mplayer plugin project at sourceforge, download, compile and put in your plugin directory and mplayer will but up inside your browser so that those embeded-only files are no longer a problem.
Thats what I was guessing it was. It would be interesting if there was a way to focus through the upper non-reflective layer w/o damaging it to isolate traces below the reflective layer. Then use a different intensity/setting/whatever to burn off the reflective insulation above where you want solder pads.
I wonder if these could be used as an inexpensive way of routing PCBs. It seems it would be more reliable way to make boards without using a drill bit which would definately be niced. They don't seem to mention it being usable on metals though.
I expected I'd need 500+mb of memory for the music I want in an mp3 player. I also want one that is small. With this drive, all we need is ogg ability and there might be an mp3 player I actually want.
While to say, "I have solved" would be somewhat incorrect since I didn't solve jack, I just put the pieces together, I can tell people how to make the audio work for this, (and the animatrix movies).
Basically, as others said, the problem is that the new quicktime movies us aac (advanced audio codec) audio instead of mp3 like older quicktime files. The solution of course is to install aac support for mplayer.
To do this, first you must install the codec. The codec that supports aac is available at audiocoding.com. It's called FAAD2. I used the cvs (1.2 beta) so I don't know if the stable 1.1 will work. (The 1.1 requires a small patch to get it to compile with newer forms of the libsndfile or forms of gcc > 3.) Other than that it compiled fine. The second change is that the libraries for faad are installed in/usr/local/lib. Apperently mplayer doesn't, by default, look in/usr/local/lib. I symbolically linked the libraries to/usr/lib (where mplayer DOES look), but I assume you could add/usr/local/lib to the search path.
Hopefully this helps many of the peopole who want to run these and other quicktime files on linux. Mplayer has made great strides and while it's not perfect, (crashes if you try to run 2 qt files back to back without restarting), it is the best there is for linux, (or for that matter any other system).
(As an alternate note, the rpm faad2-1.1-fr1.20030409.i386.rpm does not work. While it installs to the correct place, the mplayer config is not able to detect the version of faad from it.)
Printers these days are disposable. Their cheap beause they can be manufactured cheap and people buy them for price. People by ink cartrages out of necesity (which along with quality justifies to the consumer high expenses).
But if you want quality, I'd say find a HP720 or 722 , (the best personal color printer ever made IMHO), and a brother laser. (I really like brother lasers. The toner is about 30 bucks, same as a color cartrage, lasts very long, and the whole thing is small and reliable.)
While this is a reasonable step in linux's eventual takeover of the world, I really don't think it's that great. I'm sure it's very exciting that we can now play those random movies we downloaded off the internet on our pvr, but where I want native linux codecs is on my linux box. When I build a media center, it won't be an embeded system, it will be a full blown linux box with dvd, pvr, music and video playback, etc. And right now I use the windows DLL's through mplayer on my main computer all the time. So what I want is wmv and wma native to my computer, even if it isn't open source. I can live with it. The dlls I'm using now aren't.
The only really good thing I can see coming from this might be apple reliquishing and allowing someone to port the quicktime libraries to linux. While the windows codecs play great on linux, the hacked up quicktime dll's are pretty hit or miss.
Spamming must be one of the few businessess where the business doesn't want anyone to know where they are. I really can't believe a company could have legal backing to hide from those people who it impacts. I don't think the spammer has any right to privacy from people expressing displeasure at his 'service'.
Slashdot Mirror
About 2 months ago a very anti-technology professor of mine pointed out that the reason the matrix is popular is because it tells nerds what they want to hear, that they can still be cool and powerful even if where they are right now is a small room, by themselves, spending 14 hours a day stairing at a computer screen.
Oh, and man do those last pictures in the gallery remind me of the heads in a jar from futurama
out of curiosity, could they be prosecuted under any spam laws?
We'll just see how robust a server it is!
I'll have to do that. I just wanted to add EQIM since I run that some. Wasn't a big deal though since I have an icon for it on my desktop already.
Point2Play basically acts kind of like a registry for windows games. Not exactly what it does but a reasonable analogy. I wish you could add directories/executables directly to it rather than having to do an install, but other than that it's working well as a launch point for my windows games.
Over all I am pleased with wineX3. I thought the wineX3 preview was lacking but this version seams acceptable.
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/ faac login
/ faac co faad2
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot
I honestly think people just like keyboards. They work for 1 job rather well, english text input. Because of that people are rather unwilling to admit that they might have faults. But for input of anything else, they don't, (we had to develop the mouse to make up for this). The mouse isn't optimal though. It requires moving our hands to it to use and is only capapble of recording very basic gestures.
There is also of course the fact that many people don't like the idea of moving to a new input medium. There is definately a burrier to overcome in that respect, but it doesn't exist with youths who, if taught to use a 2D or 3D aparatus capable of gesture recognition, would be able to use it to it's full capability with out an unnecessary initial investment of learning.
Right now we have reached the beginning of the transition away from button inputs to gesture inputs. There are of course many projects working on gesture inputs. The first that are really viable are the 2D ones from fingerworks.com. The next will be refined versions of the P5 Glove or the sensible phantom. I think eventually gesture based input will be the type used in Minority Report, (see the 1st and 10th images in the gallery).
Finally, I think we will move on to direct input. It's been shown that people can control very simple objects, (move a ball to the top or bottom of the screen), with electrodes connected to their head. Unfortunately so far it has not been responsive enough to see application. Input may also be of the form in Ghost in the Shell where people have wireless connections through implants in their body and also physical jacks in the back of their neck. (Another thing shown in the movie are fingers that come apart on wires to type. Rather than that I'd expect a low-power data transmission in the fingers so set the fingers in appropriately shaped cavities and have the data transmitted across the skin.)
Keyboards are nice. They have worked for a long time, but it is time to replace them. Slowly we can transition from keyboards, through the 2D gesture inputs of fingerworks to 3D inputs along the lines of minority report at which time, hopefully, direct input methods will be viable.
As everyone should be aware, mplayer playes quicktime movies on linux. Unfortunately, alot of people have problems with the audio. Basically, the problem is that the new quicktime movies use aac (advanced audio codec) audio instead of mp3 like older quicktime files. The solution of course is to install aac support for mplayer.
To do this, first you must install the codec. The codec that supports aac is available at audiocoding.com. It's called FAAD2. I used the cvs (1.2 beta) so I don't know if the stable 1.1 will work. (The 1.1 requires a small patch to get it to compile with newer forms of the libsndfile or forms of gcc > 3.) Other than that it compiled fine. The second change is that the libraries for faad are installed in /usr/local/lib. Apperently mplayer doesn't, by default, look in /usr/local/lib. I symbolically linked the libraries to /usr/lib (where mplayer DOES look), but I assume you could add /usr/local/lib to the search path.
Hopefully this helps many of the people who want to run these and other quicktime files on linux. Mplayer has made great strides and while it's not perfect, (crashes if you try to run 2 qt files back to back without restarting), it is the best there is for linux, (or for that matter any other system). (As an alternate note, the rpm faad2-1.1-fr1.20030409.i386.rpm does not work. While it installs to the correct place, the mplayer config is not able to detect the version of faad from it. I've heard that it will work as long as you also install the devel package, but did not test it.)
Now, it turns out that it's pretty easy to embed mplayer into mozilla, (or in my case phoen...err, firebird). You just need to go to the mplayer plugin project at sourceforge, download, compile and put in your plugin directory and mplayer will but up inside your browser so that those embeded-only files are no longer a problem.
Because the $10,000 T-Tech machine at my school sucks. It breaks bits. It creates burrs. It's a general pain in the ass.
Marking or engraving would be all you'd want on metal. You'd be cutting fiberglass, but only isolating the metal.
Thats what I was guessing it was. It would be interesting if there was a way to focus through the upper non-reflective layer w/o damaging it to isolate traces below the reflective layer. Then use a different intensity/setting/whatever to burn off the reflective insulation above where you want solder pads.
I wonder if these could be used as an inexpensive way of routing PCBs. It seems it would be more reliable way to make boards without using a drill bit which would definately be niced. They don't seem to mention it being usable on metals though.
I expected I'd need 500+mb of memory for the music I want in an mp3 player. I also want one that is small. With this drive, all we need is ogg ability and there might be an mp3 player I actually want.
But for which media player ;-)
Basically, as others said, the problem is that the new quicktime movies us aac (advanced audio codec) audio instead of mp3 like older quicktime files. The solution of course is to install aac support for mplayer.
To do this, first you must install the codec. The codec that supports aac is available at audiocoding.com. It's called FAAD2. I used the cvs (1.2 beta) so I don't know if the stable 1.1 will work. (The 1.1 requires a small patch to get it to compile with newer forms of the libsndfile or forms of gcc > 3.) Other than that it compiled fine. The second change is that the libraries for faad are installed in /usr/local/lib. Apperently mplayer doesn't, by default, look in /usr/local/lib. I symbolically linked the libraries to /usr/lib (where mplayer DOES look), but I assume you could add /usr/local/lib to the search path.
Hopefully this helps many of the peopole who want to run these and other quicktime files on linux. Mplayer has made great strides and while it's not perfect, (crashes if you try to run 2 qt files back to back without restarting), it is the best there is for linux, (or for that matter any other system). (As an alternate note, the rpm faad2-1.1-fr1.20030409.i386.rpm does not work. While it installs to the correct place, the mplayer config is not able to detect the version of faad from it.)
But if you want quality, I'd say find a HP720 or 722 , (the best personal color printer ever made IMHO), and a brother laser. (I really like brother lasers. The toner is about 30 bucks, same as a color cartrage, lasts very long, and the whole thing is small and reliable.)
I didn't think that it covered the newest windows media codecs.
The only really good thing I can see coming from this might be apple reliquishing and allowing someone to port the quicktime libraries to linux. While the windows codecs play great on linux, the hacked up quicktime dll's are pretty hit or miss.
Try finding a cop who keeps criminals locked in his home. Ones business, the other is home life.
I just keep thinking of the robot pulling a 'crocodile dundee': walking up to someone and grabing their crotch to determine their gender.
Spamming must be one of the few businessess where the business doesn't want anyone to know where they are. I really can't believe a company could have legal backing to hide from those people who it impacts. I don't think the spammer has any right to privacy from people expressing displeasure at his 'service'.
I remember when the taco bell thing happened. I was thinking, "What the hell?!" It went on for a bit until I realized the joke.
(Yes, I'm slow. Bite me.)