MJ stops working if EWF enabled

[jerseyorig]

Hello all. Great forum! Thanks for all the info - it's been helpful! I now have a question...

I have a HP t5710 800Mhz 256/256 XPe Thin Client running MJ. I followed the famous stroths article on prepping it (removed nearly all apps, etc). However, when I enable EWF the MJ stops working after several hours - even after my scheduled nightly reboot. If I disable EWF, all seems fine.

I'm thinking of upgrading the memory to 512mb, but wonder if this is necessary given that it works fine with EWF off.

Any ideas on why EWF kills the MJ?

[momo]

I really was hoping to not hear stuff like this

recently buying a T5710 1.2GHz Thin Client (512MB DOM/256MB RAM)
I was hoping all would be functional with all TC options.

Now it makes me wonder if I should even try upgrading it with the higher storage DOM and RAM.

Transcend did say they'd refund what didn't work, but that's for just a 30-day trial period.

I was considering testing the 8GB DOM and 1GB RAM with it.

now I'm worried!

I got this for the magicjack, at least, along with other communications uses.

[PTravel]

This is just a guess, but EWF works by maintaining changes to the c-drive in a buffer. When you set it to commit, it writes those necessary changes to the DOM. It is poasible that you have insufficient memory to support the MJ's processes AND whatever permanent changes must be made to the DOM. There are some temp spaces that are mapped to the c-drive. Conceivably, whatever is being written to those and then buffered by EWF use up available memory and there is insufficient space to run the MJ.

I run MJs on t5720s, but I've never had any problem with EWF. I suspect that is because (1) the t5720 has more available memory than the t5710, and (2) I re-map temp variables to other spaces (usb drives or usb sticks).

[jerseyorig]

Thanks for the response PTravel. I attempted to map the temp variable to a USB thumb drive instead of the RAM disk. This works initially, but if I reboot (which I'd like to do automatically each night) the system hangs on startup if the USB thumb drive is plugged in... No idea why - it's just empty space (128mb). I've tried rebooting with the thumb drive plugged in with and without the temp variable set to use it instead of the RAM disk. Hangs both ways.

I imagine EWF uses the RAM disk for temp space, so using an external USB device for the temp space would probably work... just need to stop the system from hanging...

[PTravel]

The problem with external USB storage devices hanging is well-documented on HP's thin client forums. I have, however, noticed something interesting. I have a t5720 at work that runs an MJ and a few other applications, including functioning as a NAS with a 500 gb external USB hard drive. Sometimes, the external drive will cause it to hang. However, I found that if I wait long enough (sometimes several minutes), the t5720 will, eventually, boot and everything works fine.

There's also a work-around for the hang-on-external-usb-device problem. Instead of connecting the drive directly to a USB port, use a powered USB hub. That's how I got around the "non-bootable" USB thumb drive problems.

[jerseyorig]

I tried to give the reboot several minutes (about 20 actually), but it just hung... I managed to get my hands on a powered USB hub. I'll report back on how (and if) that works.

Thanks!

[rictic]

I have a HP t5710 800Mhz 256/256 XPe Thin Client running MJ.

I think that with the latest version of MJ s/w there are a couple of issues running on a HP TC with anything less than 512/512. I run a t5700 1gb DOM/512 and it runs just great. I would upgrade the DOM / memory & I think it will resolve the issue you are having...