DarkLord

RIP...

Okay, sorry nothing has panned out. Anyway, make sure and post when your 'Net service is restored so we can keep testing. Thanks!

I understand. Just try that change to DRVIN.PRG and see what happens. If nothing else, you'll have ruled it out.

Just make sure it's not just your Mega STe that's compliant. I have that here - my Mega ST4 is perfectly fine with the Y2k stuff. However, BBS Express! ST is *not*, sad to say. So when 1999 rolled over into 2000, I had multiple things that quit working. As far as my scripts went, I was able to make adjustments (taking the the 2 or 4 digit year fields completely out of the scripts, just using day and month, for example). However, some internal stuff was lost. For example, a (N)ew scan for files fails now. There's nothing for me to "adjust" here - it's internal. That's why we permanently run like it's 1999.

You'll need DRVIN.PRG in the AUTO folder first, followed by MFP.PRG. Do a "no sort" on the view option to see exactly where they sit in the AUTO folder, to make sure the order is correct. Okay, so yes, you only need MFP.PRG with any standard ST serial port. SCC.PRG is for the Atari's with extra serial ports like the Mega STe, TT030, or the rare case where someone did a mod and added another/faster serial port (I personally have never seen this done but it exists in the literature). DRVIN.PRG FASTINT = Y EXOPEN = N MFP.PRG RSVE = N REPL = U (6 TIMES) DTR = Y RBL = 256 TBL = 256 The buffers, RBL and TBL are recommended to start out at 256. You can try adjusting them from there, or I've had other users tell me that they jump in much bigger increments than 256. So try the 256, try 4096, 8192, 16384, 32768, and finally 65536 (which is the maximum, according to the docs). Something to also keep in mind, the buffers do use up memory. That shouldn't be a problem if you're running 4 megs or even a couple. So the only thing different that I can see between my settings and yours (aside from possibly the buffers) is in DRVIN.PRG. Try switching it and see what happens. From reading the docs, I interpreted it to mean that FASTINT should be Y for TOS. In the documentation I have it says the following (see what you think): "FASTINT: DRVIN.PRG is able to modify the timer interrupt of the TOS to achieve 57600Bd on MODEM1 on a 8MHz-68000. Even on MegaSTE, TT and Falcon the modification can provide some enhancements. Under MagiC the madification will never be done because MagiC (version 2.0 and newer) has already a "friendly" timer routine. FASTINT should be switched off for experiments with other operating systems or if mystic errors/behavior occur. Function (for interested users): I discovered it's enough to call the routine (GEMDOS-timer) in NEXT_TIM (negatvie LineA variable) with an IPL < 6 to enable 57k6Bd receive with an 68000/8MHz. So I insert a piece of code to set the IPL down to 5. That's not without any risk but only creates problems when other programs do such hacks too. EXOPEN: (works only if the GEMDOS-part of DRVIN is used, not under Magic version3.) "Yes" activates a very restricted GEMDOS-Fopen. It becomes impossible to Fopen a device more than ones at a the same time. It may protect (open) devices against influences of other programs on the GEMDOS-level. Normally you should answer "No", because some programs don't expect an error code from Fopen (reactions from senseless displayings till crashes) and because the program termination (normal and abnormal = crash) isn't watched, that means if the program doesn't close a device it remains open! (In few words: It's a game for developers.)" Hope this helps.

Don't get discouraged - it's all coming along nicely.

Logged in with SyncTerm in ANSI mode this evening. This is what everything looks like (noticed that your main menu screen scrolls of the top of a standard window):

Nice - looking forward to your experiences with it...

Which HD software are you using? Sometimes playing around with the amount of cache/buffers will let stubborn software run. Worth a shot.

Post the file here and give a few of us a shot at it. We'll see what happens.

Is that the Sidecart?

Not sure, but maybe start here? https://www.pouet.net/prodlist.php?order=name&reverse=1&type[]=demo&platform[]=Atari+STe&page=1

This question has recently come up on the Atari ST side of things with the PiSTorm. The Raspberry Pi here completely takes over the ST's original 68000 CPU and does it through emulation. It also offers many, many other features as well. Honestly, it is very much a "work in progress" at the moment but the potential is there. But...I've heard opinions from more than just a few that is the "brain" of the ST being taken over via emulation, so it's a no-go for these people. Keep in mind, it's still the ST's motherboard, keyboard, memory (although the PiSTorm does add it's own), all the other original chips, etc, etc,... So what do you all think? Is it still an ST or not? Even better question for this forum - if an Atari 8bit version of the Pistorm was made available, would using it make your beloved 8bit not an 8bit anymore?

Do you have the English version of HSModem? If so, the docs will guide you right through it. I'll get back on here later and try to recreate what I'm using (which will have to come from the Mega STe and not the Mega ST4 that runs DarkForce! because it uses the RSVE mod and is running at 38400).

Just to add, your BBS efforts are coming along nicely. It takes time, effort and perseverance!

I can't speak for everyone but I'm sure they would agree, we all appreciate that sentiment but... centuries?

Thanks for the update, appreciated.

That just seems...odd. I don't use BGM here. I never had a need for it. The TOS/DOS partition folders I have here, at slightly less than 512 megs each, hold thousands of files and folders...

I haven't tried any games but there's been a few posts and some video (I think) about it. I believe someone was showing Elite running on the PiSTorm (but don't quote me on that).

Everything went well and she's home. A bit bruised and sore but good to go.

I've been trying to logon but have been unable to get it to resolve? Thanks.

Love to. Unfortunately, I just got this post and my 22 year old daughter Alexia, who has POTS, is scheduled for surgery tomorrow morning at 8am for a mediport. It's not a long procedure, assuming everything goes well so if no one else has jumped in, then I should be able to login Friday evening...

Sure, try these: https://vcfmw.org/ https://vcfed.org/events/otherevents/vintage-computer-festival-midwest/

You can buy a Raspberry Pi3a+ or Pi4b from any place (like Amazon). The board itself I ordered from here: https://amigakit.amiga.store/ For some reason though, I can't get the link to resolve right now. When you do get there, you'll want to pick the PiSTorm board for the Amiga A500. That's the one that will work with ST's (not STe - if you have an STe, you'll need a different setup). You'll also want to order the PiSTorm board with the "374" latches. Follow the directions/instructions from here, exactly: https://github.com/gotaproblem/pistorm-atari Please understand that this is very much a "WIP" (work in progress) and is nowhere near complete or ready for a general release... If you have any questions, don't hesitate to ask and I'll help you anyway I can.

Welcome aboard Brian. Always good to see new people here. I don't think I'll be going to that one in Milwaukee but several of us are planning on going to the VCF Midwest event near Chicago in September of this year. Join us - it's a great show!