And building begins again!

[danfoshizzle]

neithe mine always error 10, have never had it working

[Mevi]

Plan to strip back the driver to just the essentials, rip out the 'green' functions, WOL, any other spurious stuff. If I can get it working I'll post a revised driver.

[pete]

Dan, your new build takes the XP images to a new level.

Initially just installed the Chinese version without keyboard or mouse input just to watch it boot. Very quick. I then took the EWF pieces and EFI and dropped them on Mevi's version. Both working fine using an external USB SSD. So last night moved the whole over to the internal SSD. Wouldn't boot with the Chinese EFI (acting like the nohub/hub Mevi EFI).

The VGA.ROM, xojntldr.efi, etc look to be the same as before or the with hub version.

I did notice that I can only boot the USB SSD internal Mevi version with the hub version only of the EFI.

NIC on and off boot cold and boot warm appear to be the same with the new Mevi version with or without the EFI.

When comparing the aquarium screensave; you can see its some memory thing as the regular included EFI does a slight herringbone pattern when running and the other EFI has a crisp picture. I didn't this difference when say playing back a DiVx movie.

It kind of looks like when you slow down the video acceleration. Really don't notice this though unless I run the aquarium screen saver. I don't notice it when running the clock screen saver.

Just realized that there is another difference; don't know if that would be it. When I moved the image to the internal USB SSD stick I disabled the EWF for a bit while I get stuff arranged.

I think I had the error 10 problem when the NIC would come up as not recognized; still happens every great once in a while.

[pete]

Experimenting with just the one piece its looks like just the difference between running with/without the hub EFI. (eoj versus xoj_ntldr). Not sure though why that would make a difference in the video. The xoj_ntldr doesn't run when its used on the inside USB SSD. (I can't get it to run; maybe I am doing something wrong though).

[pete]

Played a bit more switching the two on the outside running USB SSD stick and it looks to be it. I understand that the inside USB port is considered secondary to the primary one outside. Oddest thing though.

[manxam]

Pete, which EFI did you find offered the best video/performance?

[pete]

Nah, that wasn't it. But it does work well. I put on all of the Jogglers. Thank you for the great instructions.

Its definitely something in the video memory between the eoj versus xoj_ntldr files for booting. I can replicate it by just changing the EFI external USB boot from nohub to hub.

Its not really that big of an issue other than I can lock up the Joggler by running the Aquarium screen saver using the xoj file to boot.

[pete]

Best video performance is from the xoj_ntldr file when utilized with Mevi's or the Chinese EFI boot stuff from the Ghost file.

[danfoshizzle]

Never thought that the efi would make much of a difference video performance wise, thought it was all down to the iegd drivers, the drivers used at the moment are not specifically built for the joggler, rather just a generic iegd which happens to support the jogglers video resolution, I am still trying to build a new driver for the jogglers video card, I think a joggler native graphics card will offer the best performance we will see.

The chinese efi is a bit different than ours, with the grub pieces still in place and grldr found on the root of the ntfs partition, thinking maybe he had Linux on the internal memory and this is how he booted it,

still working on the new build here at my family's house, and killed another usb stick last night lol

[pete]

Dan,

Best for you to give it a try. Just configure a stick to boot either via xoj or xoj_ntldr and look to see the differences. Best to maybe even just use the chinese EFI with the xoj_ntldr. I mentioned I had recently used the aquarium screensaver and that is really how I can see the differences. But its better for you to give it a try such that you see what I am seeing.

Found an issue Dan using EWF. Yesterday I mentioned that I had enabled EWF on two of the Jogglers. Well I thought it looked to be working OK. I would disable EWF; doing my tweaking to the network connected software and reboot; enable EWF and all looked well.

It wasn't. after a bit of time the software started to act up with wierd networking issues. The other two Jogglers not running EWF didn't do this and in fact I haven't had problems with the 4 Jogglers running 24/7. I think it has to do with the way the software caches its "stuff"; but I am not sure. I am sure though that I had networking issues with the two running EWF this morning.

Maybe its just the way its configured and its interaction with the USB SSD stick. I like that it saves everything just so. Maybe I am doing something wrote when I am disabling and enabling it? I utilize two commands to disable it; one generic -disable and the other -commitanddisable.

[danfoshizzle]

Weird that it still seemed to cache stuff even though the ewf was turned off, are you using cmd commands for the ewf?

[danfoshizzle]

Do you want a gui to tinker with, will upload it with the blue dolphin this morning?

[pete]

No, I made the changes then I enabled EWF last night before going to bed. This morning looking at the Jogglers both had odd networking errors with the application; IE: vb errors. I could get to them via VNC but the response times et al were really bad; unlike anything I have seen before.

Before this all I tested was the reboot and boot stuff to see if my changes were sticking. I never tried leaving running with my "networked" applications before.

Yes I'll give it a try. With Mevi's image all I did was add the EWF stuff and went to using the Chinese EFI.

[danfoshizzle]

Sounds as though the ewf filled up your ram, will find the link in a minute, but you need to give ewf limiters, say 64mb, before it will commitanddisable automatically, then reenable itself

[danfoshizzle]

Yeah ewf is not limiting itself it sounds like, so that 496 ram we have just acts as a big old ram disk of sorts, hoarding all the stuff until shutdown then throwing at the hdd/ssd/usb, let me find that command!

[pete]

I just did the generic disable and enable command lines without anything else and the responses looked fine to the command lines.

So I would:

– ewfmgr c: -commitanddisable
- ewfmgr c: -disable

shut down and reboot.

Make my changes with whatever

then

- ewfmgr c: -enable

Maybe this was not the way to do this?

[Mevi]

Disk write filters are a bit scary to me. I wouldn't feel safe with something mission critical, anyway. I got my fingers 'burned' by Flashfire (har de har har) which committed suicide instead of committing disk writes.

Dan, I did a google search for tablet touch screen ftp blue dolphin download and found ftp://ftp.equuscs.com/drivers/120780/BlueDolphin.zip.

It's a good looking front end. I'm using it on a Openpeak Joggler. Strange how the initial screen brightness is different between the O2 and Openpeak machines. And there is still differences in either NIC FW and/or HW between the 2 Openpeak machines I now have.

[danfoshizzle]

yeah they can be all or nothing, but ewf with an easy to use gui should be better, thats where I got the dolphin from, they have an updated version now but you need to install intel appup to use it, appup itself is like a netbook app store lol

[danfoshizzle]

they are the right commands, cant find the command for the limiter, try this http://www.thevod.org/search.php?tags=m ... ion=active its a gui, there are a few out there but this looked the most promising

[pete]

Initially before going to bed response times and networking applications were quick. This morning both the Jogglers with EWF enabled had VB errors and reponse to the networked VNC remote was very slow and not really too reponsive; where as the two other Jogglers are still quick to respond remotely on the network. I have not really shut them off or rebooted them at all in the last few days.