For my project I want a Robot that I can drive using my computer, it can't be Wi-Fi based, I will not have access to internet. Does anybody have a project like that? It also needs to have a camera.
First off - you don't need internet access to set up a point-to-point wifi link; you might want to educate yourself on networking and wireless networking fundamentals, because honestly, using wifi will likely be the easiest method.
Otherwise you could do something like this:
(2.4 GHz or 900 MHz) wireless camera (on robot) -> wireless signal -> (2.4 GHz or 900 MHz) video receiver -> video capture device (USB or other) -> PC
Custom code on the PC would then handle viewing the video, integrating it with your control/command/telemetry tracking system, etc. This code would also interface to something like:
XBee or "virtual wire" TTL serial transceiver -> wireless signal -> XBee or "virtual wire" TTL serial transceiver -> Arduino on robot
The Arduino, of course, would be connected to the motors/sensors, etc - and would take commands from the PC over the wireless link, and would also uplink any necessary telemetry back to the PC custom control/command/telemetry tracking software.
See how complex that is? Also note that for an EOD system, we haven't even talked about encrypting the signal. Whereas for a standalone 802.11 system:
IP Camera ---> WiFi router/AP <---> WiFi wireless signal <---> WiFi Card or router/AP <---> PC (w/ custom control/command/telemetry tracking software)
Ethernet Arduino <---^
The IP camera would supply a simple MJPEG stream via a particular IP and port; the Arduino would be controlled and communicated with via another set IP and port (you would want the IP and port to be static, or at least a fixed DHCP assignment from the on-board router). If your router on-board the robot was beefy enough (or if you added an on-board PC - like a nano-ITX board, or a beagleboard, maybe - heck, even a Raspberry PI), it could actually host the command/control interface right on-board; set up the control software using DHTML (lots of good stuff for this, BTW, especially if you go for HTML5 tags - jack in a nice admin panel, some AJAX, a bit of JQuery).
...and for encryption? Use WPA2 for base testing; if you want better security, add SSL (with a home-genned cert) to your web server hosting the interface; and if you are really paranoid, tunnel it all over SSH or something. Basically - all the issues you'd run into with the first solution, can be more easily handled in software with the second.
That said, the second solution may or may not be as robust as the first solution; it will all depend (whichever solution you go with) on what you select for hardware. For instance, the second solution might be downright flaky over distances greater than a hundred feet or so, depending on obstacles, buildings, etc - if you used consumer hardware. If you went with professional hardware (and maybe some amplifiers, antennas, etc) - that could be made better. You'd face similar problems with the first solution as well, depending on what you used.