Posted on August 27, 2005 at 08:41 AM | Permalink | Comments (0)
|
Posted on August 26, 2005 at 10:25 AM | Permalink | Comments (0)
|
Posted on August 24, 2005 at 09:28 AM | Permalink | Comments (0)
|
Posted on June 04, 2005 at 08:01 AM | Permalink | TrackBack (0)
|
If a purpose of a weblog is to document important things so that others can find them .. I'm obligated to share the following. It's not medically related. Medical readers please ignore this .. geeks are welcome to follow along for your reading pleasure.
Our home network has three replayTVs, a win2k server, an Iomega u300 270 GB NAS (RAID level 5) .. running through a Smoothwall Linux firewall, Linksys 24 port 10/100 switch, a Lingo VOIP ATA and (finally) a Time Warner-supplied Toshiba cable modem .. which attaches us to Earthlink Broadband (essentially Time Warner RoadRunner).
I'll spare you the links to any of the above .. google will get you there rather easily.
We love the replayTVs as they allow us to avoid commercials. We almost never watch "live TV" anymore. We can also watch things when we want to - rather than when they are on. Alias and West Wing are on at the same time, but we can alwasy see them. Two weeks ago, we forgot to record Alias .. so I used Poopli to get it. Cool. We can also watch a show in the bedroom that was recorded in the Family Room. Until ...
Over the last few weeks, the replayTVs stopped reliably talking to each other. Rebooting sometimes helped .. but I couldn't figure out what in the world was going on.
Last night I invested (wasted?) three hours and figured this all out.
After researching similar issues on the REplayTV FAQ and the AVS replyayTV forums, I learned that this problem is often due to the ReplayTVs having different TIME settings. A difference of over 30 seconds is bad.
So I went through the processes that everyone suggested to cause the devices to "phone home" and find out from the ReplayTV mother ship what time it really is. They're using a NTS protocol .. which runs on UDP port 123, BTW.
But none of the devices could get a new time!
So I looked at the firewall settings to amke sure that port 123 was open .. and it sure was ..
And then I looked in the firewall logs and saw that the poor firewall hadn't updated its time successfully in weeks. Every time it tried to call a time server, it failed.
So I logged in to the Lingo ATA .. which was no small task. I still can't get in with the admin password (thinking maybe that would have helped me to solve the problem .. so if anyone knows how .. let me know!) .. but the user password (username: user - password = ph3taswe) .. log in to 172.25.25.1 through a browser .. and I noticed that the ATA has successfully made IP entries for DNS servers (it's getting DHCP from Roadrunner) but that it also has an entry for NTS .. which says "0" ... so I'm guessing that the ATA is intercepting all NTS requests and sending them to the NTS that it knows about ... which .. in this case .. is "0" .. so all NTS requests fail.
I'll bet that if I could get in to the admin interface, I could change the NTS address to something useful (it even looks like the Roadrunner DNS servers are running NTS) .. but I can't.
So at this point (1 AM last night) .. I had two choices:
a) Connect the firewall directly to the cable modem. This would cause me to lose the QOS that the ATA presumably is giving me (though this may motivate me to add a QOS mod to the firewall).
b) Install NTS on the Win2Kserver .. and use the firewall to redirect all requests to UDP port 123 over to that server. The time would be consistent within the network - even though they would not likely be "right" according to the Atomic clock.
I Chose option "a" since I want the ReplayTVs to work with Poopli . and I think that other ReplayTVs will need to be able to talk to mine .. so they will all need to agree on the time.
This option worked. ReplayTVs now can tell the time, and Lingo phone quality doesn't seem too bad. We'll see what happens when streaming TV shows across the network.
Posted on February 06, 2005 at 07:20 PM | Permalink | TrackBack (0)
|
At the office, we have great custon-built scanning software that Dave built. It's worked flawlessly for 3 years now .. and aside from the fact that the TIFF files it makes are a bit bigger than they need to be (hin, hint Dave) ... it's grrreat.
I'm looking for something now to use at home that is just as easy to use. This is not rocket science .. so I'm surprised that no company has yet produced software that does this elegantly. If you know of one .. please leave a comment.
The crieteria for a quick and easy scanning solution:
What I've found so far:
edrawer - personal version is inexpensive .. but I can't download a demo .. and their website is so poorly designed it makes me wonder about their skills at making usable software. I can't tell where the files are stored, but it looks like ley are ina database. I don't want my files trapped in a database in 10 years. I want them in the OS -- in hierarchies of folders. They won't be trapped when the scanning software company goes out of business and my software won't work in Windows 2015 .. or Windux .. or Mac OS XV.
PaperMaster. hmm .. looks enticing,, but again .. where are the files?
SinmpleIndex "the best value in scanning software" .. sores files in folders. Inexpensive. Downloaded the demo. Scans a few images just fine .. then .. crash .. over and over ..
If you want to make sales .. then make sure your demo works.
Douxplorer is a "document managerment systerm." It works. But it stores the files in the database .. which has to live on your hard drive .. unless you pay for the professional version (n which case you can store the "library" (databse) on a server or shared folder.
InfoThek Docudex is the winner so far .. as it seems to do everything I want .. and it's developed elegantly. I'm going to test it for a while to see if I can make it work well.
Posted on December 13, 2004 at 06:14 AM | Permalink | TrackBack (0)
|
"Bandwidth" is the amount of data a website consumes/generates/requires over a given period of time. Since building Medlogs.com, the bandwidth consumed by my account on our web host has increased quite a bit. How ironic that a successful weblog or public service site like Medlogs will cost (rather than earn) the owner more money.
Last month (october, 2004) we used nearly 12 GB of bandwidth ... and one morning our sites were down because we had gone over the limit of 10 GB. So today I'm experimenting with gzip compression to improve the speed of page downloads on both Medlogs and Docnotes. There are several ways to enable gzip, but the simplest is to use php:
At the beginning of every document (or add it to the MoveableType template) insert this line:
<?php
ob_start("ob_gzhandler");
?>
Of course, if it's already a php document, you can omit the <?php ... ?>
This will imporve performance on Medlogs.com and will reduce the amount of bandwidth that we use.
Blogrank.org is coming soon too ;-)
Posted on November 01, 2004 at 07:28 PM | Permalink | TrackBack (0)
|
IT digest discusses the present and future of google.
Here's my idea for another feature .. which I'll bet wouldn't be too hard to implement:
"publish this" in gmail would be a way to publish an e-mail to a weblog. It would need to support a publishing API so we're not all locked in to blogger.
oh .. I've got a few gmail invites .. if you want one, post a comment here.
I'll get back to medicine soon.
- JMR
Posted on September 09, 2004 at 06:22 AM | Permalink | TrackBack (0)
|
I passed the boards. Was worried that I didn't .. but I ended up doing pretty well. won't have to do that again for 7 years. Phew! ..
Going on vacation for a week. Bye!
Posted on August 16, 2004 at 10:19 AM | Permalink | TrackBack (0)
|
Our old Netgear router has been acting up recently and instead of buying a new one, I installed a free software router onto an old PC we weren't using. Smoothwall is a great router and it also provides firewall, DMZ, etc. I have not gotten it working with DansGuardian yet, but hope to soon to protect my children from the Internet.
Installing Dansguardian into Smoothwall doesn't look too hard, but I am no linuxhead .. so this may take a bit. 1st attempt this morning didn't go so well.
Posted on July 06, 2004 at 06:38 PM | Permalink | TrackBack (0)
|
Recent Comments