Splents

I’ve been developing my remote security cameras for a few months now, although progress has been quite fast in the last week.
I’m getting the prototype PCB’s made up, hopefully these will allow me to put my first camera into production.

The main goals of these cameras is long duration event triggered surveillance.
Current systems that are supposed to achieve this are aimed at the hunting market, where visual size and start-up time are not an issue.
In remote human surveillance, the demographics of the target make development of these devices difficult.
In catching poachers, vandals and trespassers – capturing photos and video that allow for facial recognition is the main goal.

The security system runs on 12v power, which means any solar panel, car battery, and other power generating paraphernalia can help sustain the unit for months.
The sensors are completely removable and customisable. The sensor design is open, so that anyone can add-on pressure sensors, infra-red sensors, noise sensors etc.

Will have some photos of development soon.

Backtrack 4 supports the use of the ZTE MF626 out of the box.
While there are plenty of tutorials on how to connect the device, it took me a while to figure out why I could not see the device /dev/ttyUSB0.

When you plug the internet stick into a Windows based operating system, a virtual cd-rom is created. Once the software is installed, inserting the device runs the autorun.exe.
Obviously linux can’t use the system libraries in order to perform the same action, so what you will need to do is eject the cd-rom in linux.
The easiest way in backtrack 4 is to pop open the Konqurer->Storage Devices, hit refresh and you’ll see the cd-rom. Right click and eject.
Now, if you head to your console and type lsusb you will note that you have the correct drivers loaded, and /dev/ttyUSB0 will be available for your choosen modem dialer to use!

Sorry folks – The demand for the backtrack images (especially the old ones… *looks suspicious*) was far too high for my server, and was ruining the availability of my other websites (that actually earn me money).

So for the meantime, I’ve removed the backtrack images. I’ll be keeping the S-T-D and BCCD images up.

Last night I managed to get a strong signal from Optus C1 with my mish-mash of satellite receiving equipment. It was my intention to work on producing a smart card as part of my academic interest in satellite technology. After reading up on the “Irdeto 2″ cipher, and the function of ecm’s, emm’s and cas values, there wasn’t going to be an easy way. I need some more equipment. For the meantime, I’m going to stay on to Ku band and see what else I can pick up. I would be particularly interested in moving amateur UHF, but I’m yet to come across any satellites that claim to be for that purpose.

New patch was released for Bad Company 2 today for Steam users – which is very exciting if you’ve been having troubles with the game.

More information for the patch notes/change-log.

I’ve added the Battlefield v1.5 Patch to my mirror. Depending on where you are in the world, this may be available to you faster than on other servers. The information about this patch is on the EA website in the Battlefield 2 section. There are also a list of localised mirrors.

Get Battlefield 2 v1.5 Patch from splents.com.

Note: You MUST install the v1.41 patch in order to get 1.5 to install.

I would also say that version 1.0 of the game do not make a registry key titled ‘Version’. For the patch to install you need to create this key. I can’t remember what it is but if you Googled around you would find it.

I had this problem where I would go to play a game of Battlefield 2 (Single Player or Multiplayer), and when I would get to the spawn screen the mouse would just be frozen.

It hadn’t done it before, and I had been playing both the retail version of BF2 and the Steam version. Turns out it is caused by a profile conflict. All I did was delete my profile from the ‘Documents’ folder and away it went.

This poster had the same problem and solved it by deleting his Battlefield 2 Profile.

So you’ve suspected that there are hacks in the game all along, but haven’t had the evidence…

This is about as good as the evidence will get, and unfortunately Infinity Ward are either incapable or unwilling to address the problem.

From a technical point of view, I find the hack funny. Having said that, I’m sick of rage leaving games because some n00b is using tools similar to this. Ah well.

So you’ve noticed that whenever you get into Call of Duty: Modern Warfare 2 you get this annoying “NAT Status: Strict”, or perhaps more annoying – when you and your friends try joining the game lobby it says unable to connect, and counts the connection attempts up until it throws an error.

You’ve followed the borderline offensively abandoning instructions left on Infinity Wards website, with still no change.

Well  I have a few more suggestions that have so far worked for everyone I’ve shared them with.

1. You have additional network adapters – perhaps from VMWare, perhaps physical. Try disabling all but the one you need for internet in the network control panel. 90% of the time, it works every time.
2. You have uPNP disabled in the network control panel. Enable it

Restart Steam and see if it helps. Hopefully it does, because usually this means you won’t have any more squad trouble.

I’m currently hosting S-T-D and Backtrack distributions in the mirrors folder. These can be used with my rainbow tables, or for a whole range of fun activity’s.