Jump to content

jamm

Members
  • Content Count

    632
  • Joined

  • Last visited

Community Reputation

539 Excellent

2 Followers

About jamm

  • Rank
    Dragonstomper

Profile Information

  • Gender
    Male

Recent Profile Visitors

846 profile views
  1. The letters actually don't matter - they're more there for human readability. It's only the number that matters. For example: MST+7 -- This says you're 7 hours west of UTC and you don't observe DST MST7 -- This is the same ABC7 -- This is also the same XYZ7 -- Same... ARIZONA7 -- Same! MST-7 -- You're 7 hours east of UTC, probably somewhere in Russia or Vietnam MST+7MDT -- This says you're 7 hours west of UTC and that you change your time by 1 hour during DST MST7MDT -- This is the same MST7MST -- This is also the same MST7ABC -- Same! ARIZONA7WILDCATS -- SAME! The reality is that time zones, and, more importantly when DST time starts and ends for your particular region, are not only complicated, but they change from year to year and region to region. So there's no reliable way to compute them without a database or rule set that describes them, and that database needs to be updated as things change. "Full size" operating systems will have a database like this from which you can pick a location (e.g. "USA/Phoenix") and the TZ and DST rules for that particular location have been helpfully provided by someone. They'll be out of date (ha!) sooner or later, so unless updates are provided somehow, you'll find the operating system will not switch to DST time on the correct dates. Notice in the examples above we didn't specify when DST starts or stops. There are built-in defaults: if you specify any letters after that number, then you observe daylight savings that changes the time by one hour starting on the first Sunday in April at 2:00AM and ends on the last Sunday in October at 2:00AM. (The specific defaults chosen can change from one operating system to another.) If those defaults don't work for you and you want to provide the correct details, you can do so like this: MST+7MDT+6,M5.1.0/01:30,M9.1.0/1:30 That says you're 7 hours west of UTC during standard time, and you're 6 hours west of UTC during daylight savings. Daylight savings starts on the first Sunday of May at 1:30AM and ends on the first Sunday of September at 1:30AM. The "MST" and "MDT" there are just to give humans something to read. Anyway - I thought that was an interesting diversion... We'll put a drop-down list in the web interface to make it easy to pick something for most people, and you'll be able to override it manually if those options don't meet your needs.
  2. I added a couple of font files that probably put things over the edge on WROOM boards. If you remove the two TTF files in the /DATA/WWW folder you should be fine and it won't affect operation.
  3. The N64 and GameCube were underpowered compared to the competition. The difference is, by the time the Wii came around, it was clear that Nintendo had made a conscious decision to not try to fight Sony and Microsoft on the hardware front. You might say the same thing about the GameCube, but I think with N64 it was just a case of underestimating how Sony was going to shake up the market. The N64 was released in mid-1996, while the PlayStation was out late-1995. It couldn't be designed to be "on par" with PlayStation because there was not enough time to make significant changes to the N64 and the PlayStation represented a new direction for console gaming. Edit: I got the date wrong on the PS release - it was out in late 1994 in Japan. So I don't know what Nintendo's excuse was for not doing better than they did with the N64 other than they were the undefeatable market leader at the time. (Though you could still argue that they didn't have a lot of time to react to PS.)
  4. Just to add to what @tschak909 said above and maybe elaborate on what I said before that: TNFSD does no enforcement of security itself. Therefore, all the security enforcement must come from your operating system's file security settings in the folders you've given TNFSD access to and the rights it has by virtue of what user context it's running in. Obviously you don't want to run TNFSD as root or Administrator...
  5. A foretold by the prophecies, the next firmware update will provide a simple mechanism for changing FujiNet's HSIO index setting via the web interface. This will, of course, make its way to the Atari config program later on.
  6. Please do not put anything on TNFSD that you don't have backed up elsewhere. Little to no effort has been put into securing that code (either by the original author 10 years ago or us in our recent additions), so assume any folders you expose via TNFSD are public and may be destroyed/altered. Professionals get this stuff wrong even when they're trying, and we're not even trying...
  7. I'm curious how long that would take to print on a real 1020, but I'm not willing to sacrifice one to find out...
  8. I have to admit, it's kind of a kick that you guys are able to share Atari files directly now. 😬
  9. Think of all the money you saved by not wearing those little pens down to even smaller nubs.
  10. We talked about this on a side channel, but for the benefit of everyone else: the problem only presents itself at POKEY/6, which is currently the high speed mode FujiNet defaults to in order to maintain compatibility with SpartaDOS. POKEY/0, and probably other high speed modes, don't seem to be a problem. This will be addressed indirectly when FujiNet gives you the ability to change the high speed divisor setting manually. Coming Soon™
  11. All the details, including the XEX in question, are just a couple of messages above this one. I don’t know enough about what’s happening in Yoomp’s loading routines to say what’s happening, but it clearly behaves differently when different SIO speeds are in play.
  12. Well, I'm pretty glad you raised it. I wasn't aware of that particular behavior in some software, so it's good to know for next time someone asks. Plus, we know your WiFi is solid. And it's good to know someone's actually testing things out. We honestly need more of that. This also raises the issue of allowing you to change the SIO speed dynamically via the web page. Something we talked about a while back but hadn't gotten around to yet.
  13. And I just tested with RespeQt. It also fails and freezes at POKEY/6 and works at POKEY/0. FujiNet is the only one that seems to handle switching back and forth between normal and high speed SIO properly when the latter fails. At least in Yoomp. Here's RespeQt's output at POKEY/6: Serial port speed set to 68522. [AutoBoot] Get status. [AutoBoot] Read sector 1 (128 bytes). [AutoBoot] Read sector 2 (128 bytes). [AutoBoot] Get chunk 0 (287 bytes). [AutoBoot] Get chunk 1 (2 bytes). [AutoBoot] Get chunk 2 (352 bytes). [AutoBoot] Get chunk 3 (256 bytes). [AutoBoot] Get chunk 4 (128 bytes). [AutoBoot] Get chunk 5 (422 bytes). [AutoBoot] Get chunk 6 (2 bytes). [AutoBoot] Get chunk 7 (61 bytes). Serial port speed set to 19200. [AutoBoot] Get chunk 7 (61 bytes). Serial port speed set to 68522. [AutoBoot] Get chunk 8 (123 bytes). Serial port speed set to 19200. [AutoBoot] Get chunk 8 (123 bytes). [x5]
  14. Well, I just tried it with Lotharek's SIO2SD. Same problem at POKEY/6, except it completely fails to load about halfway through. POKEY/0 is fine.
  15. Debug output is your friend! Ok, so the interesting thing about both your test cases is that it there's a checksum error after 16 sectors of the XEX are read. Same spot in both your TNFS and SD loads. Very unlikely that those are random errors... So that made me think of the other thing that's different between my setup and yours: I'm running at POKEY/0. By default, the firmware is built to support HSIO at POKEY/6. We did that because it gets along with SpartaDOS's HSIO routines whereas POKEY/0 does not. So I rebuilt for POKEY/6 and I have the same problem you do. I believe what's happening is that Yoomp's custom SIO routines (the ones @tschak909 was talking about) kick into effect after 16 sectors. I don't know the details, but they either don't mess with anything if they see POKEY/0, or something unexpected happens with POKEY/6. So, I don't think it has anything to do with the bootloader, but Yoomp itself. It'd be interesting if you tried loading Yoomp with SIO2PC or another drive emulator set to POKEY/6 and see if it gets along with loading Yoomp.
×
×
  • Create New...