unless you have an EXT2 filesystem

I believe that you can only get this as a user-mode library. Last I checked, Microsoft were charging a fortune for the Installable Filesystem DDK. The licensing terms probably preclude using "viral-licensed" code, as well.

There used to be a free one I believe at http://tarzan.cr.cyco.com/~andreys/ext2fsnt/ but it's now part of a commercial product and you have to buy it. It's $30 so it's not that expensive though...

I've never personally used it so I've got no idea how good it is.

- Trevor

OK, so Mark Lord thinks my stuff is cool

As soon as I have it stable I will kick something out (pre-built binaries and the source) so everyone can try it out or just comment on my coding style

The problems at the moment are that the kernal only apears to start one network device, so I have disabled the built in one to get the USB emulation working, it shouldn't be a big change to get them both going, but that is not my priority at the moment. Once I have things stable on my MK2 I will get to the same stage on my MK1 so all those people can get HiJacks cool features too (which is why this thread was started wasn't it )

iMaGe, Trevor is correct in saying that this is just a USB device still, the HW in the Empeg is still doing a lot of the work, and it would be impossible to emulate a host port (like the one on your PC that you can actually plug a keyboard into) in just software.

I actually started on this task as I was looking at how to connect USB devices, and Drakino suggested this may be a nice little warm-up task. For the discussion on connecting USB devices see here, and don't worry as soon as I have this one nailed my focus will switch back to that one.

So, what's happenin' Dude?

The world awaits..

Haha... Mark gets back at all the users (e.g. me) who ask about how the docks are coming along! (Or what's going to be in the next Hijack release..)

Work is rapidly heading towards project milestones, and we are in the middle of customer acceptance, so 12hour days are the norm here. Plus We are due to complete on a new house next Friday so we are doing walks and inspections on that as well as trying to pack up all the stuff from where we are at the moment.

Hopefully things will settle in a couple of weeks and I can finish it off then.

In that case, leave him alone, I am getting enough cr@p at work without being hassled here

PS. anyone got a HP N class server they don't need, our compile times just went through the roof and having a machine under my desk would be nice

Too bad. I just returned an unutilized 8-way 16GB rp7405 demo unit today.

unutilized

"utilized" (or "utilised") is overutilised . Just settle for a plain "unused", please.

Well if you find any more that are unused feel free to send them my way

Oh, it was used. It just wasn't utilized. It was doing stuff, just nothing useful.

hi, i've an iPAQ 3630 (with pocket pc 2002) with both USB and SERIAL sync cables. i've got a "female (normal) USB" to "male (little) USB" adaptor like this http://www.national-tech.com/specs/30u1-03300.htm that permits to physically connect the iPAQ to my MKII via USB. is there a chance to share a file in the empeg HD (possibly over tcp/ip, i'm thinking to a divx .avi) to be used with the iPAQ ? if the answer is yes, is it possilbe to do it with the USB sync cable and pocket pc 2002 ? if no, will it be possible if i'll install familiar linux over the iPAQ ? i've no budget for a pcmcia jacket and a pcmcia eth adapter and to use the USB sync cable will be a real legend for me thanks for help

What ever happened with this project, is it integrated into Hijack now?

Hey Chimaera (Mark),

Could you please grab the code you had for this, warts and all, and post it here for us. I would really like to have this working now, and possibly port it to some other plaforms as well (eg. Receiver, Central, ..).

Just post it. No work, no changes, we'll deal with it!

Thanks

I was just curious where does this project stand?

Lost. The original author never made his code available to us, and all has since vanished. Such a shame.

I may have a go at it in a few months, but it would be much better (and more likely to get done) for someone else to do it. This is not particularly difficult to do, either. A good intro to Linux kernel development.

Cheers

Hi Mark,

Well the work isn't totally lost. Last year turned into a complete nightmare for me, work got pretty busy (imagine project managing a SW project similar in scale to Karma, but shipping over 800K units per month), plus I had a close friend die and spent a month or so flying back and forth between the UK to deal with that.

I didn't actually see your message to send him the source, I wasn't ignoring him. But infact I had only a couple of days ago got out my dev machine and started to set everything up again, only to find a dying hard disk, so I have copied off all of the files, and I am waiting for a new disk to arrive, then I can set up the machine and get going again.

Sorry it has taken so long, but hopefully I can get going on this again and get it finished as from what I remember I was getting pretty close.

Hey, welcome back!

Thanks,
According to the UPS pages, I should get my disk tomorrow, kick me hard (via PM) if you don't hear from me by Monday!

Okay, good.

I've patched your ethernet emulation code (untested, and slightly hacked) into the Hijack v365 source tree, to be released shortly. It is NOT compiled in by default -- use "CONFIG_EMPEG_PEGASUS" to configure it.

Any new patches anyone wants to send in should be based on the code now in Hijack.

Thanks Mark!

cool. how is this supposed to work, anyways? plug the usb cable in and (j)emplode thinks that its on then network?

The code in there emulates a Netgear FA101, so when you plug it in and load the Netgear drivers Windows thinks it has a new network card. From that point you need to set all of Windows settings for the network card, IP address, subnet etc... Also you need to give the Empeg a static IP address (differant from the one you just gave to the PC, but reachable from the settings you just gave the PC).

The Empeg should magically apear to a device on your network, or atleast until it panics the kernel .

I am working on trying to fix the problems, and will let Mark have any patches once I come up with them.

COOL! question... Netgear FA101 is included in the included drivers, right? this is great. no more using a cross over cable at my friends house. just borrow one of the already connected usb peripherals. question... does the empeg think it has a network connection also, therefore letting us do network stuff? ping, ntp, wget, etc?

Netgear drivers should be downloaded from the netgear website. I chose that adaptor as it had a Pegasus chipset that appears to be supported by Windows, Linux and Mac although it has only been tried on Windows.

Yes the Empeg thinks it has a network connection, ping works fine, everything else PANICs the kernel.

Also another note, as the Empeg only appears to bring up the first ethernet interface, the version that is in the current Hijack will disable the built in ethernet when you do a build that enables the Pegasus emulation, this will be fixed, but it is in the queue after the kernel panics.

And for those who don't know, when he says "the kernel panics" he means it crashes...

...
empeg usb initialised, PDIUSBD12 id 1012
Writing to endpoint 5
Ack Only!!
USB Int: 128
USB Int: 0
empeg state support initialised 0089/88c1 (save to d0005980).
empeg RDS driver initialised
...

installed latest hijack, and it seems that i have this in my bootlog now. something to do w/ PEGASUS? thought it shouldn't be configured by default.

oh man.... i'm just seeing the potential.... imagine jEmplode saturating the bus completely with a dual-headed upload to both the usb-ethernet and the regular ethernet. i'm aware that there won't be much of an improvement, but any additions help.

That is debug trace from the USB code, a quick look at the actual patch Mark used it looks like the functionality is disabled but the debug trace is still enabled (for the original USB code), hopefully nothing to worry about

Those are just harmless debug messages, which happen to be on the pathway of the "regular" USB code. I imagine they'll get DEBUGed out in a later release.

EDIT: Hijack v369 will be out shortly, with the Pegasus debug messages removed (ifdef'd out).


Cheers