I'm not a EE or RF guy, but would the ISM band [wikipedia.org] be of any use in this case? It is unregulated, after all.
ISM isn't unregulated, it's unlicensed. You don't have to have a license to operate on ISM band, but there are specific rules about using ISM band, and you have to abide by those rules or you get to write a check to the FCC and/or spend some time in jail.
One of the rules governs maximum power output, and it's pretty low, like 1 watt or thereabouts. If you're trying to control a UAV from miles away you probably want more than 1 watt of transmit power.
The ones I've been buying recently have been marked "soft white". They're not the same as an incandescent bulb, but they're close enough that my wife doesn't complain about them (like she did with older CFLs).
Yep, I agree. It seems much more likely to me that this type of mail is from buggy/misconfigured spamming software than from spammers trying to "untrain" filters.
But then again... Twenty years ago I was working on a small project using Logitech Modula-2, part of which involved copying files. My file copying code was nothing fancy - allocate a large-ish buffer (large being 16KB or 32KB or something like that - this was on a 640KB MS-DOS box), read from the source file into the buffer, write the buffer to the destination file, repeat until done. When I ran the program the file copies seemed to be really slow, and after comparing the copying time using the Modula-2 program to copying from the DOS command prompt the file copying was indeed quite slow. For no good reason I fired up a low level debugger (SymDeb or Debug or something) and started digging into the compiled Modula-2 code. It turned out that the Logitech runtime library had helpfully "optimized" my "read 16KB into this buffer" call into a series of 512-byte reads and buffer copies.
The powerlines in my neighborhood are underground and there are plenty of fire ants around. So far (8 years) the fire ants have been much more interested in biting me than touching any power lines.
Although I'm glad my employer paid for it rather than myself, because those machines are impossible-to-upgrade lead balloons nowdays.
Amen to that. I have a few older but still decent PC's at work that are essentially stuck at 1 gig because upgrading them to 2 gigs of RDRAM would cost more than a new PC.
As I understand it, IEEE 1588 requires special hardware in order to achieve its full accuracy. My guess would be that on non-special hardware (i.e. a typical PC) it's not going to achieve any better accuracy than other network time protocols.
Tivo can move recodings off the tivo onto the server.
Tivo can talk to other tivo's in the same house and move recodings around.
Yes, but it's godawful slow at network access. A one-hour show takes about one hour to move to another Tivo or to a PC. Moving the same file from one PC to another takes about one-tenth the time.
The pool guys have been talking of implementing a $company_name.vendor.ntp.pool.org setup. Having the $company_name specificity would allow them some leeway if an individual vendor does something silly. I don't know if any vendors have bought into this though.
Your mini-van is probably built a lot differently than your SUV, and is probably safer for other vehicles if you are ever involved in a collision. See TFA's diagram of the frame design differences between a Honda Odyssey mini-van and Dodge pickup. (A lot of SUV's are built on the same frame as pickups.)
Cheap mass market GPS's don't make very good time sources for NTP. They don't output the NMEA text on the GPS second, and they don't output the NMEA text at precise 1-second intervals.
There are inexpensive OEM GPS boards that include a precision PPS output that work very well with NTP.
Getting the IT idiots to open up the NTP port seems like the easiest thing though.
The TFA mentions two teams of scientists who found the object independently of each other. It doesn't say anything about discovery by an amateur astronomer.
The knock with EPA estimates of hybrids' mileage is that the EPA estimates apparently don't provide a valid comparison of hybrid vs. non-hybrid mileage.
Someone must have missed that Hubble is not in geosynchronous orbit.
I use tin snips. They work pretty well, and you can find them at any hardware store.
ISM isn't unregulated, it's unlicensed. You don't have to have a license to operate on ISM band, but there are specific rules about using ISM band, and you have to abide by those rules or you get to write a check to the FCC and/or spend some time in jail.
One of the rules governs maximum power output, and it's pretty low, like 1 watt or thereabouts. If you're trying to control a UAV from miles away you probably want more than 1 watt of transmit power.
The DIY HTPC won't do CableCard, and your inexpensive tuner cards won't do HD. If you want that functionality the expensive Tivo is a good choice.
The ones I've been buying recently have been marked "soft white". They're not the same as an incandescent bulb, but they're close enough that my wife doesn't complain about them (like she did with older CFLs).
Yep, I agree. It seems much more likely to me that this type of mail is from buggy/misconfigured spamming software than from spammers trying to "untrain" filters.
But then again... Twenty years ago I was working on a small project using Logitech Modula-2, part of which involved copying files. My file copying code was nothing fancy - allocate a large-ish buffer (large being 16KB or 32KB or something like that - this was on a 640KB MS-DOS box), read from the source file into the buffer, write the buffer to the destination file, repeat until done. When I ran the program the file copies seemed to be really slow, and after comparing the copying time using the Modula-2 program to copying from the DOS command prompt the file copying was indeed quite slow. For no good reason I fired up a low level debugger (SymDeb or Debug or something) and started digging into the compiled Modula-2 code. It turned out that the Logitech runtime library had helpfully "optimized" my "read 16KB into this buffer" call into a series of 512-byte reads and buffer copies.
NTFS paths can be up to 32767 characters. Or so i read - I'm too lazy to try it myself.
The powerlines in my neighborhood are underground and there are plenty of fire ants around. So far (8 years) the fire ants have been much more interested in biting me than touching any power lines.
Amen to that. I have a few older but still decent PC's at work that are essentially stuck at 1 gig because upgrading them to 2 gigs of RDRAM would cost more than a new PC.
Avast! is good stuff.
Link works, but it wants a codec I don't have.
As I understand it, IEEE 1588 requires special hardware in order to achieve its full accuracy. My guess would be that on non-special hardware (i.e. a typical PC) it's not going to achieve any better accuracy than other network time protocols.
Tivo can talk to other tivo's in the same house and move recodings around.
Yes, but it's godawful slow at network access. A one-hour show takes about one hour to move to another Tivo or to a PC. Moving the same file from one PC to another takes about one-tenth the time.
The pool guys have been talking of implementing a $company_name.vendor.ntp.pool.org setup. Having the $company_name specificity would allow them some leeway if an individual vendor does something silly. I don't know if any vendors have bought into this though.
Yeah, I've been running Virtual Server 2005 R2 for a few months. It's been working fine.
TFA doesn't have an official announcement, and linked articles in TFA don't have any official announcements.
Your mini-van is probably built a lot differently than your SUV, and is probably safer for other vehicles if you are ever involved in a collision. See TFA's diagram of the frame design differences between a Honda Odyssey mini-van and Dodge pickup. (A lot of SUV's are built on the same frame as pickups.)
I like Avast!, and it has the coolest name of any AV software.
(Yes, that's an opinion. Feel free to disagree.)
There are inexpensive OEM GPS boards that include a precision PPS output that work very well with NTP.
Getting the IT idiots to open up the NTP port seems like the easiest thing though.
The TFA mentions two teams of scientists who found the object independently of each other. It doesn't say anything about discovery by an amateur astronomer.
OK, I was lazy and didn't start downloading from MSDN until this morning. Right now MSDN downloads are running slower than I've seen in several years.
I'm glad MS is getting in the game. More people will take BT seriously, and I'm sure the BT folks will continue to improve BT.
The knock with EPA estimates of hybrids' mileage is that the EPA estimates apparently don't provide a valid comparison of hybrid vs. non-hybrid mileage.