FWIW, I always assume (and take it as a given) that whenever the OSD locks up during a recording (remote non-responsive and red light on [when it shouldn't be]), that I have to reboot.  I don't even think of it as being that much of a hardship anymore.

Yep, I share this. Soft-reboot may not properly reset the DSP, thus causing the DSP initialisation (loading kernel modules) to hang on boot.

Why this happens I've no idea. I had quite reliable recording when using network shares, but SD cards were not so good. Possible if vrecorder cannot write out fast enough, it gets overwhelmed, and then DSP gets stuck. Or OOM kills it. Hard to know. Neuros spent a lot of engineering time working on it, to some improvement but not perfection.
-G

Don't forget that most of the recording work is done on the DSP.

I think killing vrecorder just stops it fetching data from the shared-buffer with the DSP. This probably makes the DSP hang, waiting for the buffer to be cleared. There is no easy way to reset the DSP afaik, since e're missing public APIs and docs for any form of DSP control.
-G

You had a peek in this firmware and you couldn't see anything usefull because you must disassemble DEX file.

The file extension DEX you found is for Android applications. The DEX format of the n100 firmware is quite different.
Looking at the DEX in a hex editor, the parts of the firmware I recognise are intact, just the header is different. It might be possible to open it up, but to be honest I have no real ambition to do so. It was merely an exercise in curiosity.
-G

Hey,
from what the community has gathered, the n100 is a cut-down version of the OSD. Neuros wrote the customised for Emtec, writing some closed-source apps for their needs. I've never seen or used one, so I don't know much.

1. It's year 2011 (EMTEC n100 released in 2007/2008). Is there any upgrade (firmware, anything...) avaible for this device?

Not that I know of, no.

2. Someone heard any news about programing/changeing something on EMTEC n100 by Neuros group or freelancers?

A little, but not much. I had a quick look at the firmware file to see if I could open it up and hack around, but it appears very different to the OSD's firmware files. It may be obfuscated or encrypted.

I myself did a little freelancing customising the OSD firmware for surveillance tasks. But the n100 is an unknown quantity to me.

3. Does EMTEC n100 support overwritting file when disk space ends? (I don't want to end recording after space end)

Probably not, as the OSD doesn't do it by default (see below).

4. If it doesn't support overwritting after end of space IS THERE ANY GOOD HEART MAN WHO COULD EDIT FIRMWARE AND ADD SUCH OPTION?

Well if someone could figure out how how the firmware is being protected, then it would be possible to change the open-source code.

5. Did anyone use this gadget as surveillance device (with composite cinch camera)?

I'm gathering this is your intention. The OSD has been used as surveillance recording device by various people. It can be easily scripted to enable a sort of auto-overwrite.

6. Does it support 1TB HDD's?

Yes. Preferably using FAT32.

I wish you luck!
-G

I suspect WPA2/AES might need some level of hardware support?

Not sure. I'd've thought the CPU could do it too. But after some Googling, I can't find any mentions of WPA2 support via this chip. You could be out of luck
-G

I thought in the Windows that if a wireless card didn't support more advanced encryption options, that Windows would do the encryption instead. I'd try using Window's Wireless utility to set up the connection and dump the supplied crappy utility.

Something like this was added to XP in a service pack or patch. Maybe you can get it going.
-G

Hey,
From http://wiki.debian.org/zd1211rw I see that support for this chipset is available from the 2.6.18 kernel version. But OSD runs 2.6.14 unfortunately, so you'll need to do some kernel hacking.

I remember Nero working on enabling USB wifi devices (rt73 chips I think) a long time back. There are traces of it in the Arizona firmwares, for instance "wireless-tools" is installed by default. But if I'm not mistaken, he gave up on it because its behaviour was unreliable. I think he blamed the USB driver in the end.

I wish you luck.
-G

I'd try a Factory Reset, hit the Xim button while at the main menu, you'll see it there.

More extreme solution could be a firmware re-install. But sometimes it can help.
-G

I can supply the x11vnc executable, the IR script, and the shell script that I use to launch it (that corrects for some, er, undocumented problems features in the program).

I think this is exactly what the OP wants. Would you mind?
-G

I think it's gone. I requested this over a year ago, to no avail.

I'm sorry to the OP, I searched but failed to find my copy of x11vnc. Recompiling it wouldn't be hard, but his IR script was good work.
-G

Hey, GarBage wrote firmware for the DAC, not for the OSD.  Don't blame him! 

Har har

Obviously you're at fault for making your OSD crash like that Garbage in...

I think the files are stored on the read-write storage, so CF card in your case. Hopefully it's still there. Try /media/ext/.osd-extended/scratch
-G

Lame.

If you've not tried any other recording with your OSD since, telnet in and see if you have any strange files in /media/ext/data. Called something like osd.* maybe. I need to check a recording log.

You recording to FAT? or FAT32? I've heard ext2/3 is more reliable.
-G

IDA Pro 5.0 which is freeware for Windows.

...but doesn't do ARM. I have the v6 demo version (does ARM and x86), but it is huge. And it is ridiculously expensive with support for several dozen processors I'll never touch. Overkill, no?

Oops, my bad. I've the demo version too, not the 5.0 freeware one. I'd not buy it either.
-G

Inconceivable! What about:

• objdump -d (if you can compile using the OSD's toolchain on Windows, then you can use it's arm-linux-objdump binary to disassemble)
  
• IDA Pro 5.0 which is freeware for Windows.
  

Remember, people in masks cannot be trusted
-G

P.S. much respect for building your own disassembler. *much* respect. What could you possibly want to disassemble?