The simulator is ready. I decided to change how I packaged it to reduce build times, so it's similar to kugel's now, in which the Linux and Windows sims are in one zip archive. All parts of the sim should be working, including plugins, codecs, etc. If something isn't working, let me know. Build time now takes about two minutes, but that shouldn't be a big deal.
The link is http://chrisjs.com/rockbox.sim.zip.
Again, feel free to post comments/suggestions/problems.
I have a Linux simulator ready, though it isn't in the update script yet. I also have a Windows copy of the simulator compiled, but I haven't tested it yet, although it should be ready in the next few hours. If there's any problems with it, feel free to let me know. I do know that the estimated runtime setting will cause it to crash, because I had to add a few if statements so that it will compile. I'll try to fix that sometime soon.
Links:
Linux: http://chrisjs.com/rockbox-sim-linux.zip
Windows: Not released yet
Sorry about the nearly two hours of downtime. My host was having "file server" issues, even though it seemed like it was just a failed apache process. I had submitted three support tickets, but it still took a while for them to fix it. Again, sorry for the downtime.
I plan to add a simulator to my build tomorrow, after I get some sleep and trim the filesize down a little. The sim will be added to the update script, though it may be possible for me to also have it compile a Windows copy as well. I can't say for sure whether the Windows sim will compile, but I'll see if I will be able to get it to work.
We're getting closer to USB support!
There hasn't been a patch for roughly five days, so there isn't anything I can add to the build yet. However, it's already gotten a lot faster in the past few hours - read was 56 kB/s earlier today, and now write speed is up to 349kB/s. While it isn't close to the OF (3 to 4 MB/s) it's still nice.
Since I've been getting behind a little, I figured I might as well post a decent way to make sure I get a new patch (or anything else) added to my build. If you email me at requests at nuclearscripting dot com (I need to change that address soon...I'm moving away from that domain) it will be directed to the same email address that I use to check for patch updates. While I get roughly 10 or so (sometimes up to 25) emails per day from the Rockbox tracker to that account, I only move patches after I have completed what's in the email (ex: if there's a patch with a sync, I will only move it to another folder after I update the patch in my build). By emailing me at that email address, I won't be able to miss it, even if I am away.
I think there may be a problem with the way I have the patch list set up. The database seems to use the old patch instead of the new one, which is causing the new patches to not appear. I'm going to be away for the next few hours, but I'll see if I can get it fixed sometime soon.
Not exactly Rockbox related, but nonetheless, it seems SanDisk is preparing to release a new device - the TakeTV. There's a subforum on the Sandisk Forums for the TakeTV, but no information. The trademark for it was filed on July 18 (http://tess2.uspto.gov/bin/showfield?f=doc&state=k1s490.2.1). I don't know much else about it (there doesn't seem to be much information) but I might be able to ask if anyone wants me to.
The cache of texas.gs.shi.com mentions the TakeTV:
4GB Sansa Taketv Video Playerusb 2.0 Integrated Remote Support
The DIVX website also mentions the TakeTV.
That seems to be the only information I can find. Googling "Sansa taketv" and "sandisk taketv" only show 9 results.
USB support could be available tonight, as Zagor (Bjorn Stenberg) had said earlier today in IRC (http://www.rockbox.org/irc/reader.pl?date=20071016#12:20:54). There's a patch in the tracker that's about a day old with the USB code, but I'm wondering if it's worth adding it. If the proper USB code is released tonight, it'd probably cause quite a few problems with SVN. However, if anyone wants me to add it, feel free to let me know.
The automated build update should be fixed now. For some reason - I'm guessing I changed permissions - the build user was refusing all ssh keys, which was preventing the automated updates. I've fixed it now, and am monitoring it to make sure there aren't any problems.
