2 Jogglers - One boots XP One Doesn't

[jmwhooper]

I've got myself 2 jogglers to use as windows based home automation controllers and all I can say is wow, they are great!

Only problem is, one of the jogglers boots into the foshiz mini xp/2003 build every time first time via a USB stick and the other one using the same USB stick doesn't. Both are running the exact same O2 firmware and software versions.

The error I get booting the 2nd joggler is the "Int 37 Trigger at........ Ignoring...." followed by "Patch #0: Not found" and "Patch #1: Not found".

Any ideas?

Also, if I want to add Windows components like scheduled tasks to the foshiz mini build how would I do that, the "add remove windows components" doesn't work.

Thanks all for the great work getting windows installed, it has made my home automation plans so much easier!!

[Mevi]

Hmmm, that's interesting, just one Joggler. I HAVE seen that error, but it's sooooooo long ago that I can't remember what causes it. Now, have you changed anything on the internal storage on either Joggler? Is there a hub connected (you gotta use port 4). The modded bootloader is very choosy about such things.

Dan might be able to answer whether task manager can be added to his build, but if you don't mind using a 3rd party app, there's System Scheduler which is freeware and downloadable from their www.splinterware.com website. It's much more feature packed than task manager and you can also automate key presses and basic mouse interaction. I use it and can recommend it.

[jmwhooper]

I'm running both jugglers identically, no internal mods and no hub just a USB stick in the side port. The only difference externally between the 2 jogglers is that the good one is model number A02JOGXN and the other is A02JOGON

I'll take a look at the scheduler software.

Thanks

[pete]

I have seen the OpenFrame2 boxes stuck booting XP with same error. Look to see if you have an OpenPeak Openframe box versus an OpenPeak Joggler box. They are different hardware and will both run the O2 OS software. They are labeled differently; one being OpenPeak and the other being Joggler. Here I am using the XP'd Seabios'd clients for my Home automation Homeseer touch screens. With the Seabios they will boot just fine from cold or warm boot and just fine off of the USB stick or PATA drive. Much faster booting than EFI and 100% booting. That said though the BIOS doesn't work with the internally built in NIC card so I use an externally mounted connected to a 2nd USB interface inside of the Joggler.

Here I utilize an always running on board client to remote the touchscreens; IE: screen off at night, screen savers, wave and TTS stuff, et al.

[jmwhooper]

Pete, what am I looking for to see if it's an Openframe vs Joggler box? Both mine look identical externally with the only difference being the model number on the rear label. When booting the good one has the O2 logo and the other one an Openpeak logo, but I did flash it with PnPiii and put the Openpeak OS on there so not sure if that would have changed the logo.

I did come across a Seabios thread and would be interested to see if that would work, is there a "how to" thread somewhere to get it running, I'm great at following instructions but not so good going at it cold!

[pete]

The OpenPeak box is labeled Openpeak (engraved) on the box where as the Joggler is labeled O2 Joggler on the box.

The booting logo is just the firmware on the box.

IE: if you followed the PnP3 directions you put a new base clean firmware on the box then followed by the PnP3 script and software.

The Seabios would do the best for you relating to just XP today. It is "an experiment" in vivo and not complete. That said though read through the entire thread first. You can install the BIOS and then fall back to the original OpenPeak bios easily. I have now 5 Jogglers running Seabios'd XP, 3 Jogglers running EFI bios XP and the rest are running PnP3, XBMC and Squeezeplayer. They are all over the house and I am driving my wife nuts as now have 3 in the master bedroom and two in the family room.

I did a quick step by step to install the Seabios in the seabios thread. You need to be careful though and do baby steps.

[Mevi]

Pete's instructions on the thread are very clear and easy to follow.

There is also instructions to unpatch Joggler versions of XP to run on SeaBIOS right near the end of the thread.

One other thing..... are you using his foshiz v1 or v2? There are different versions of the EFI bootloader out there. It seems like the bootloader is not able to find the patched NTLDR or NTDETECT on the active NTFS partition.

Pete, does my XP build also not boot on the openframe Jogglers?

[jmwhooper]

@Mevi. Looks like I used the V1 build on this tread http://www.jogglerwiki.com/forum/viewto ... ?f=2&t=367. Have found the V2 build but the download links are dead, are there any img download links available?

@Pete. Both are etched on the back with O2 Joggler. I might take them both apart and see how they compare internally! I'll have a go at the seabios version too.

Thanks

[jmwhooper]

Well, I was playing around with my USB HDD with the foshiz mini build and ran the no hub.cmd file, when I booted again the int 37 errors still appeared but this time it booted, so I now have 2 Jogglers booting XP and I'm very happy!

[hawsey]

Well, I was playing around with my USB HDD with the foshiz mini build and ran the no hub.cmd file, when I booted again the int 37 errors still appeared but this time it booted, so I now have 2 Jogglers booting XP and I'm very happy!

Glad you got it working can you keep us posted regarding your joggler home automation endeavours I.e what software /hardware and what you are controlling please as there are a few on here would be interested

[pete]

@Mevi

Pete, does my XP build also not boot on the openframe Jogglers?

It works fine on the Openframe Jogglers. Never had an issue. I have though converted all of the Openframe Jogglers now except for one to Seabios.

It didn't boot right on the OpenFrame2 Jogglers. I haven't paid much attention though to it.

Today I decided to pay attention some more. Note this is only on the Openframe 2 devices.

It would boot on and off. I kept seeing wierd geometry errors and interupt errors and int 37 errors.

I cleaned up the partions on one set up with GParted. This made it boot just fine via a direct USB connection.

I have been able to get it to boot once via a USB hub though; so playing some more now.

@jmwhooper

Yes; have a look inside and compare the inside to the pictures on the Wiki. Tell us what you see or better yet take a picture of both sides of the motherboard if you can?

BTW Which other EFI booloaders are there? I do have the third one which used grub (from China). What other ones are out there?

[Mevi]

Ah, yes It's the early version of the bootloader that didn't support hubs. Dan and I kept it as an option as it knocks a chunk off the boot time. Seems to not to mind that int37 error, whatever it means. I had 5 Jogglers to test with, but they were mostly well behaved, no oddball versions of the hardware.

Great news that you've got 2 XP Jogglers now.

Pete, I don't have any Jogglers or my disk images easily to hand anymore (it's been more than a year since my last XP release!). Does build 3 default to the nohub bootloader on the disk image?

[Mevi]

There was the original v1.0 bootloader which from the displayed text on screen, appeared to be very close to the XP ON MAC bootloader that it was based on and also credited that project on screen.

I think there were a few others, i forget the version number Dan used for his groundbreaking first, but it's the later ones we use over here on this forum now. I think Eric Huang still has the different versions of the bootloaders and their source code on his blog... I reference and link to that blog in the 'how to make your own XP...' wiki. I forget if it's English language or if you'll need to translate.

[pete]

Yup.

Now I am thinking that there might be four bootloaders.

Here while still playing with the EFI stuff I created a base EFI boot set up with every bootloader I had and kept them in separate subdirectories. I would just copy over to the EFI root whichever flavor I wanted to play with.

I've since lost track and will need to revisit this.

BTW I have your last build now running just fine on the OpenPeak 2. (doesn't work with a USB hub though).

I was going to put the Corebios on one of the Openframe 2 boxes this week. Even though I cannot open it there are two external USB ports on it which will work for me.

[jmwhooper]

Now up to 3 Jogglers and about to get my 4th. Also have ordered a few KingSpec 8GB SSD USB sticks to boot from.

After a week or so of constant running of the foshiz mini build on both Jogglers, I can say overall I'm pretty happy. The only minor quibble I have is that the clock seems to reset and even with TClock and a scheduled task to run every few minutes to resync it doesn't always work. Does anyone have a more reliable way to keep the clock up to date, or any idea how it gets out of sync even when the Joggler is left on the whole time!

[pete]

My currently running XP EFI booting Jogglers have done the best with the Kingspec 8 Gb SSD USB sticks. You can also utilize this stick with the Seabios/Coreboot stuff redoing the boot stuff keeping the base. It'll run even faster. I've also tested the USB to SSD (ZIF) and that is even faster.

I am particular somewhat about time in general. That said I have an NTP server in house connected to a GPS receiver and do my own time stuff.

I changed the boot such that it goes a bit slower. I also run Tardis as a service and replaced MS stuff for time sync.

[jmwhooper]

I purchased the KingSpec sticks off your recommendation, I don't want to do the soldering thing and I'm happy wit the speed of the current set up for the limited use it needs to support.

The time thing isn't the be all and end all for me, I won't be using them for any time based functionality once I get them running with my home automation gear, but at the moment they are being used as an XP (or 2003) photoframe and calendar, just so I can leave them running and keep an eye on them.

Any ideas if the clock resetting to Jan 1 2005 is down to Tclock attempting to sync and not being able to, or is it something with XP that is doing it?

[pete]

I have found out experimenting that using a USB to ZIF SSD drive in Seabios mode is almost as fast as the soldered PATA port ZIF SSD drive. That said I have one Joggler in this mode working well today. This methodology is solder free.

Easiest was for the time thing is to run a script in the beginning to set some random date to this year; then wait until the network is up then utilize NTP to sync. This will slow down the boot process a bit but not by much. I quite using TClock and just went to using tardis. Another thing I do though is remote control the XP Jogglers and send a time sync remotely to them from the mother ship. You can do this also easily from another computer that is on 24/7 via wintel or linux. This is what I am doing for all of the Homeautomation connected touchscreen Jogglers; then again I NTP time sync internally versus using the internet.

IE: The HA mothership is monitoring all of the touchscreens in general whatever they run. Once the mothership HA machine sees that they are up it'll send commands over to the touchscreen. IE: making the Joggler be just a screen saver, running XBMC, SB or propietary Touch screen client. That said before running an application via remote control its does some base checking of the client including the time stuff.

I have noticed a battery backed up RTC setup on the Openframe 2 boxes which works well now.

[Mevi]

I setup a scheduled task running as the SYSTEM user (as the command line window is hidden) to sync the time with wtime32 on my builds. I didn't use tclock to sync, just to display a nicer looking clock. I set the sync to run everyday from 1.1.2005 at 00:02am and 00:03am. Unless the Joggler is powered off, it holds it's time OK through a soft boot.

To get wtime32 to update without complaining that 2005 is too far in the past, you'll need to edit something in the registry to increase the accepted date/time variance to something HUGE. The maximum should keep it running happily until 2050 or something. The registry setting.... Well, I can't remember what it is and all my stuff is packed away. I found what I needed with a Google search.

Even with this setup, it's not bullet proof... Occasionally, it doesn't update the time. Oh, and find a decent time server. I used ntp.org which has a pool of servernames for around the globe.

You seem happy with 2003, but if you get stuck on something, a keyword search through the build 3 thread below might find you some additional useful stuff that we came across over the months.

[pete]

Thanks Mevi!

I started to play with time this morning on one of the Jogglers as I have been remote sending over the date after booting from a cold boot.

I did find my settings were at just a few hours. The new default for W8 is 48 hours. That said though I changed it to MS max settings.

IE:

Using regedit and going to CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection and MaxPosPhaseCorrection and adjust these two to:

0xFFFFFFFF

hopefully will work.

I cannot get net time to work with my NTP server as it errors out.

I do see the NTP time server with Tardis though and Windows time server which doesn't make any sense to me.

C:\>net time
Current time at \\ICS-AT-ST-03 is 2/5/2013 2:49 PM

The command completed successfully.

C:\>net time \\192.168.244.159 /set /yes
System error 5 has occurred.
Access is denied.

C:\WINDOWS>tardisnt debug
2013/02/05 14:52:04.67,Debug: RFC868 TCP Server started
2013/02/05 14:52:04.67,Debug: RFC868 UDP Server started
2013/02/05 14:52:04.67,Debug: RFC867 TCP Server started
2013/02/05 14:52:04.67,Debug: RFC867 UDP Server started
2013/02/05 14:52:04.69,Debug: SNTP Server started
2013/02/05 14:52:04.69,Debug: SNTP Client started
2013/02/05 14:52:04.69,Info : SNTP Client connecting to 192.168.244.159
2013/02/05 14:52:04.69,Debug: SNTP Client Ver: 3 Stratum: 1 Mode: 4 Poll: 10 Precision -8
2013/02/05 14:52:06.50,Info : The time has been corrected by 1.798 seconds (Clock stepped)
2013/02/05 14:52:06.50,Debug: From: NTP Server By: 1.798 seconds (Clock stepped)