I have an iMac running Snow Leopard 10.6.8 and I own a HP ScanJet 3670 Scanner.
HP gave up attempting to support this scanner and the accompanying software years ago, but some people have figured out how to give it life again.
You computer is going to freak out if you try to install the software for the HP ScanJet 3670, but everything goes great if you install the same software but tell the installer you actually want to install it for the ScanJet 3690. Here is how you go about it.
1.) Download an old scanner multi installer from HP's FTP site:
ftp://ftp.hp.com/pub/softlib/software8/COL16498/sj-43494-2/COL16498.dmg
2.) Install it. It is old junky software so be aware of a few things. After you put in your administrator password it'll act like it has stalled for a couple minutes (just wait it out). You'll select ScanJet 3690 after that. The software will also forcibly quit any applications you have open so make sure you don't have anything unsaved. If you are viewing this website it'll close your browser. After the installation is complete it will force you to restart your computer.
3.) Upon restart you'll notice two icons in your dock. If you are like me you don't want them there, so trash them. HP will do it's damnedest to force them back in your dock so go checkout your Accounts in System Preferences, find Login Items and remove both of the HP Scanning tools.
4.) Scan stuff. It should work just as well as you could ever hope.
I have read reports that this trick works exactly the same in Snow Leopard as far back as 10.6.2 but your mileage may vary. Anybody know if the ScanJet 3670 will work in Lion? Leave a comment about what Mac OS X system you have gotten the scanner to work in.
Wednesday, February 29, 2012
Monday, December 12, 2011
Build Mencoder from source on Debian Wheezy
su
apt-get install subversion
svn checkout svn://svn.mplayerhq.hu/mplayer/trunk mplayer
apt-get install build-essential
apt-get install git
apt-get build-dep mplayer
[install debian-multimedia]
apt-get install libfaac-dev
cd mplayer
./configure
[press enter]
make
make install
mencoder -oac help
apt-get install subversion
svn checkout svn://svn.mplayerhq.hu/mplayer/trunk mplayer
apt-get install build-essential
apt-get install git
apt-get build-dep mplayer
[install debian-multimedia]
apt-get install libfaac-dev
cd mplayer
./configure
[press enter]
make
make install
mencoder -oac help
Friday, September 30, 2011
Setup Apache2 on Debian
Apache2 works great on Debian, but you need permissions set properly...
Add yourself to the www-data group.
Add yourself to the www-data group.
sudo usermod -a -G www-data [username]Change the group that owns /var/www/
sudo chgrp www-data /var/www/Change the folder permissions
sudo chmod 2775 /var/www/
Friday, July 8, 2011
Debian Sudoer Group
Everybody wants to sudo.
Debian wants you to sudo.
It's just not as easy as it should be.
Here's the simple way to do it.
Debian wants you to sudo.
It's just not as easy as it should be.
Here's the simple way to do it.
aptitude install sudo
usermod -G sudo <username>
Monday, May 9, 2011
Slimbox Previous Next Buttons Always On
I wanted Slimboxes Previous and Next Buttons to be always on, always visible, so people who haven't used lightbox style image displays can fully understand how things work. Nobody had much worthwhile, so I had to dig in.
Turns out it's pretty easy.
Just replace the lbPrevLink and lbNextLink codes with the contents of the :hover and delete the :hover psuedo class.
Turns out it's pretty easy.
Just replace the lbPrevLink and lbNextLink codes with the contents of the :hover and delete the :hover psuedo class.
#lbPrevLink {
left: 0;
background: transparent url(./slimbox/prevlabel.gif) no-repeat 0 15%;
}
#lbNextLink {
right: 0;
background: transparent url(./slimbox/nextlabel.gif) no-repeat 100% 15%;
}
Thursday, February 10, 2011
Making a New Remote Branch with Git
This works for me at work. I can't guarantee it'll work for anybody who doesn't work with me. We'll be creating a new branch called "new-feature."
First checkout the branch you want to branch from.
$ git checkout master
Make sure ever thing is updated (fix any problems that might happen here).
$ git pull
Check you are in the right branch (note the asterisks).
$ git branch
$ git branch new-feature
Checkout the new branch
$ git checkout new-feature
Double check you are in the right branch and the remote branches are good
$ git branch -a
$ git push origin new-feature
Triple check your branches to make sure everything shows up as expected.
$ git branch -a
Other developers who might also want to use the new branch can now easily do so. If they do git branch -a the new branch will show up on the list as a remote branch. If they want to actively work with the branch they need to check it out to their local machine.
$ git checkout -tb new-feature origin/new-feature
First checkout the branch you want to branch from.
$ git checkout master
Make sure ever thing is updated (fix any problems that might happen here).
$ git pull
Check you are in the right branch (note the asterisks).
$ git branch
* masterCreate new local branch
staging
$ git branch new-feature
Checkout the new branch
$ git checkout new-feature
Double check you are in the right branch and the remote branches are good
$ git branch -a
Push local branch to create remote branch* new-featuremasterstagingorigin/HEADorigin/masterorigin/staging
$ git push origin new-feature
Triple check your branches to make sure everything shows up as expected.
$ git branch -a
* new-featuremasterstagingorigin/HEADorigin/masterorigin/new-featureorigin/staging
Other developers who might also want to use the new branch can now easily do so. If they do git branch -a the new branch will show up on the list as a remote branch. If they want to actively work with the branch they need to check it out to their local machine.
$ git checkout -tb new-feature origin/new-feature
Friday, January 21, 2011
Setting Up Tomcat and Eclipse in Ubuntu Tutorial
This had me scratching my head for several days, but I finally put all the pieces together. If you want to get around to building some JSP stuff in Tomcat using Eclipse on Ubuntu (or some other Linux) you might run into some problems like I did and just complete a simple Hello World tutorial. Here's the problems and the solutions.
Problem: You don't have an option to create a new "Dynamic Web Project"
Cause: You don't have the Web Tools Platform installed.
Solution: Download WTP. If you already have Eclipse you can update installation here.
Problem: You are getting any slurry of errors about permissions or can't write or can't find or can't configure errors. They are all varied and confusing and difficult to google. So you probably won't find this page by looking for them.
Cause: You are using the default Tomcat installation from apt. This saves you from worrying about the installation, but it isn't setup the way Eclipse wants you to.
Solution: Run the commands found here. I've archived them incase the forum ever dies or changes drastically.
sudo apt-get install tomcat6
cd /usr/share/tomcat6
sudo ln -s /var/lib/tomcat6/conf conf
sudo ln -s /etc/tomcat6/policy.d/03catalina.policy conf/catalina.policy
sudo ln -s /var/log/tomcat6 log
sudo chmod -R 777 /usr/share/tomcat6/conf
Problem: You get an error about port 8005 and 8080 already in use.
Cause: Tomcat is already running on those ports so they are of course in use.
Solution: Tell Eclipse to start it's Tomcat on a different port. Use the directions found here. I've archived the text incase the page ever dies or changes drastically.
Click on servers tab in eclipse and then double click on the server listed there
Then when the config page opens change the port by clicking on the numbers and typing over them
Problem: You are getting weird Java errors about objects not found or classes or something.
Cause: The Hello World you are attempting to run is way over your head.
Solution: Try something simpler to make sure your Tomcat and Eclipse setup is working properly. The example from IBM is old but simple. I'm not going to archive it for you.
Problem: You don't have an option to create a new "Dynamic Web Project"
Cause: You don't have the Web Tools Platform installed.
Solution: Download WTP. If you already have Eclipse you can update installation here.
Problem: You are getting any slurry of errors about permissions or can't write or can't find or can't configure errors. They are all varied and confusing and difficult to google. So you probably won't find this page by looking for them.
Cause: You are using the default Tomcat installation from apt. This saves you from worrying about the installation, but it isn't setup the way Eclipse wants you to.
Solution: Run the commands found here. I've archived them incase the forum ever dies or changes drastically.
sudo apt-get install tomcat6
cd /usr/share/tomcat6
sudo ln -s /var/lib/tomcat6/conf conf
sudo ln -s /etc/tomcat6/policy.d/03catalina.policy conf/catalina.policy
sudo ln -s /var/log/tomcat6 log
sudo chmod -R 777 /usr/share/tomcat6/conf
Problem: You get an error about port 8005 and 8080 already in use.
Cause: Tomcat is already running on those ports so they are of course in use.
Solution: Tell Eclipse to start it's Tomcat on a different port. Use the directions found here. I've archived the text incase the page ever dies or changes drastically.
Click on servers tab in eclipse and then double click on the server listed there
Then when the config page opens change the port by clicking on the numbers and typing over them
Problem: You are getting weird Java errors about objects not found or classes or something.
Cause: The Hello World you are attempting to run is way over your head.
Solution: Try something simpler to make sure your Tomcat and Eclipse setup is working properly. The example from IBM is old but simple. I'm not going to archive it for you.
Subscribe to:
Posts (Atom)