Where exactly would he plug this newfangled usb flash thing in at?

The laptop will not have any USB ports.

Do yourself a favor and pay attention. Look the report i mentioned up too.

They go into explicit detail with statements from congress on the passage of the 1996 telecom act as well as previous FCC interptetations and state it is clear congress never intended the internet to be regulated other than an information service. They even mention VoIP in it.

In other words, the lawsuit to reverse this has already been laid out. Congress never intended the internet to be regulated under title 2 and congress has not changed any laws since then. You have a modern FCC who overstepped its abilities and was shot down by the courts, now all the sudden they ignore over 2 decades of interpretation of law and without any legislative action at all, moved around the courts. Of course they will lose the lawsuit.

then I'll care about what "prominent members of the U.S. House of Representatives and the Senate" think about climate change.

Take a look at what James Inhofe (R-OK) who is chairman of the fucking Senate Committee on the Environmentthinks of global warming. TRIGGER WARNING: IF STUPIDITY UPSETS YOU DO NOT CLICK.

http://www.slate.com/blogs/fut...

Test equipment is allowed to transmit and receive on those frequencies. If it looks like a radio, it can't. I have a number of cellular testers hanging around here that can act like base stations, mostly because I buy them used as spectrum analyzers and never use the (obsolete) cellular facilities. Government has different rules regarding what it can and can't do in the name of law enforcement, although FCC has been very reluctant to allow them to use cellular jammers.

If you can afford it, something from Ettus would better suit your application.

Actually this is probably the best answer. I like this better than my own answer of using a serial link.

I even have such an adapter, and didn't think of it.

The Laplink idea was copied by Microsoft. If it has one of the more recent versions of XP, you can use a serial link.

You did not say how recent the destination machine is. If it has a serial port and XP or 98, you can just use a null modem cable. If it's a newer machine, you will have to use a null modem cable AND a serial-to-usb cable or adapter on the newer end. Further, if you are on Windows 7 or later, you will have to install Virtual PC and then XP mode (both free from Microsoft), so you can run a virtual XP window.

Then start up serial networking and transfer your data. One machine is 'host' and the other is 'client'.

PCMCIA CF card reader, plus fat formatted CF card, plus USB CF card reader.

Or about a thousand other ways.

Because "It's Simple! All You Have To Do Is..."

Not just managers. Even working for yourself won't save you. Customers as well.

Boy, does that take me back!

Now get off my lawn!

And that's when you re-negotiate, or quit.

From my experience, it's easy to make bad estimates because bad estimates are easy to make. If it's a big project, take your worst possible guess, and multiply by 1.5.

One of the biggest reasons bad estimates are so easy to make, is that the stakeholders "forget" to include too many of the details. And even, sometimes, some of the big essential features. It's debatable how many of these things are really "forgotten", versus not known or just intentionally left out to lower the estimate.

Therefore, I go about it this way:

I write out clearly what the specs are. Often this is just a repeat of the stakeholder's own specs. I estimate each major "feature" in the specs.

My standard contract states that this is only an estimate, based on the written scope of work just described. If at any point it looks like the work will take more than 10% over the estimate, it is time to examine why and the terms must be re-negotiated.

If any significant changes or additions are made to the scope of work, the terms must be re-negotiated.

These stipulations make sure everybody is talking, and if anything goes over estimate, everybody knows why. It also makes sure that if they add more work, I get more money.

I have a third stipulation I put in every contract: single point of contact. The stakeholder(s) must appoint one person, and one person only, who is to give me instructions and discuss the specifications. Nobody else, even the CEO, is allowed to do that.

I insist on these. So far, I have not had anybody turn me down because they thought the terms were unreasonable. That last clause keeps me from getting caught between conflicting instructions from different people. Other than that one, these are SOP for many engineering contracts. I just borrowed from those.

At least you could get in. I had to change my resolution so I could find the edge of the login option. It was hidden under the search box.

Now that I'm in I'm still seeing overlapping options along the top edge.

Brings to mind the Maxell ad where the guy is sitting in the chair, hair blown back by the JBL-L100 in front of him.

Imagine the paper tapes instead of the L100. Except no hair would be blowing back, and I suspect the fellow would be asleep. Other than that, exactly the same.

To answer your question about connectivity, the device has 10/100 Ethernet with the Linux networking stack built in.

That's excellent. Did you build your own protocol, or did you use the mechanism RFSPACE, Andrus, AFEDRI and the various USB-to-Ethernet servers have established?

I try -- hard -- to support all ethernet based SDRs for which I can obtain protocol information.

It also has USB-OTG, and I already know WiFi and USB Sound Cards work with no additional work.

Sound card I/Q is no problem for SdrDx -- that gets the RF in, and of course I support that. The problem with the rest is controlling the SDR's settings: center frequency, attenuator, sample rate, and so on. This is because of the radical differences in USB interfacing from platform to platform.

Having said that, if you've got a working command line utility that talks to the control systems on your SDR, then SdrDx emits information via TCP that can be used to drive the command line client from a script. We've pulled this off with the Peabody and Softrock SDRs pretty well. Again, though, we run into the issue of which platform(s) the utility is available for, seeing as how they'd have to be radically different from one another.

Smith actually wrote that it was necessary for the government to intervene when monopoly or oligopoly loomed. He said that was necessary to keep everybody working within the bounds of free market.

It worked pretty well with telephones for 40-50 years. Granted, significant corruption was leaking in toward the end, but for a very long time the ill effects of monolithic monopoly were kept at bay, while we kept the advantages (i.e., world's best interoperability, reasonable rates for their day).

During that time, in some countries in Europe which allowed competition in the market, you couldn't call the neighbor on one side because he was using a different phone company, and even the respective voltages were not compatible. And you couldn't call the other neighbor on the other side, because she was on yet a different company. And there were 3 times as many wires on the poles.