Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - elmer

Pages: [1] 2 3 4
1
Turbo EverDrive / Re: Any way to back up BRAM to TED v1?
« on: August 11, 2020, 08:14 PM »
The TEDv1 doesn't have any RAM at all, and so the Tennokoe Bank rom is unlikely to be patchable to run on it.

The BRAM backup tool that is in my TEOS replacement OS for the TEDv2 could possibly be broken out into a standalone HuCard for the TEDv1 ... but it wouldn't be trivial (because the TEDv1 and TEDv2 access the SD card a little differently), and it's not something that I'm likely to ever do myself.

The source code for the critical parts of the TEDv2 SD card reading and writing routines are on my github if someone else has a TEDv1 and wishes to take on the task.

2
I don't think it's possible to make the TED simulate a backup accessory either.

You're right, it's not possible on a TED/TED2.

The regular 2KB of backup-RAM is in bank $F7, and the TED2 only maps banks $00-$7F (which is the full range of HuCard banks).

3
Turbo EverDrive / Re: Issues with TED V2.5 and CD Unit
« on: May 14, 2020, 08:43 PM »
Ok but as far as I can tell all Super CD-ROM games I chuck at it are working fine without crashing and I also found this little nugget of info on this post from elmer the author of the patch: https://krikzz.com/forum/index.php?topic=3640.msg34306#msg34306

"As a side-effect, it also means that translation teams and homebrew programmers have a full 512KB of RAM to use.

The other side-effect is that it means that Turbo Grafx CDROM and PCE Briefcase owners can use the TED2 instead of buying/using a Super System Card"


Yep, that's correct, the TED2 will happily act as the extra 192KB of Super System Card RAM ... in fact you need to run the patched BIOS that was released years ago so that the TED2 doesn't cause problems on a DUO/SuperCD.

Or if you run my TEOS replacement for the TED2, then you can run an un-patched BIOS, and TEOS will automatically patch it to work safely.

There is still the fact that you're best off running the Japanese version of the Super System Card BIOS on your TED2, because some games aren't compatible with the US version of the BIOS.

Both Gate of Thunder and Dragon Slayer 2 have issues when running with the BIOS in RAM on the TED2, but both games can be patched to fix this.

The patched BIOS that I released includes the fix for Gate of Thunder, but not for Dragon Slayer 2.

The patching that TEOS does automatically includes the fix for both games.
 

4
Tennokoe Bank support, built-in BRAM backup tool and fixing Populous?

It also supports patching the System Card 3 (both Japanese and American) at runtime in order to avoid the potentially-damaging bus-fighting on the TED2 that was reported years ago.

That means that you no longer need to run my patched copy of those on your TED2, and you can go back to using the original verified-correct dumps of those HuCards, which is nice for purists.

The latest System Card 3 patch in TEOS also fixes the crash that was found in "DRAGON SLAYER - THE LEGEND OF HEROES II" when it is run with the TED2 operating as the Super CD RAM.

The problem isn't really because of the TED2, it is because Dragon Slayer still has some development-system code in it that should have been removed before shipping, and that code gets confused when it sees all of the TED2's RAM.

5
EDIT: Is the KRIKzz update just for the button swap? I didn't see any save functions, unless I'm just being derpy.

AFAIK the button swap is the only significant change in KRIKzz's latest OS, so nope, no save functions.

When I tested it, I still get the graphical glitches in Populous that lots of folks have reported over the years, too.

That's definitely something caused by his OS, because I don't have the same problem in TEOS.


Anyway ... I've updated the file link in the message above to the latest TEOS beta 4.

6
Either support for Tennokoe Bank or adding an option to the Everdrive menu that can copy between the backup RAM and SD card. Or both.

While it's great to see KRIKzz release a new version of his OS yesterday, I was sad to see that there weren't more new features in it.

In strangely coincidental timing, I released a public beta of my replacement OS for the Turbo Everdrive yesterday, too.

While it actually does have support for running the Tennokoe Bank software, it is much easier to use its own built-in BRAM backup functionality.

Anyone that wishes to try it can download it here ... TEOS Beta4.


Just extract the archive, and copy the files to the root of your Turbo EverDrive's SD card.

In particular ... the contents of the /TBED/ directory *must* go in that directory.

If you have already got some of those files in your /TBED/ directory, then you must have been running an earlier beta version ... please do NOT overwrite those specific files, or you will lose your BRAM saves.

While you *can* theoretically rename teos.pce to OS.PCE and put it in your /TBED/ directory, and it should work, I do NOT recommend doing that at this point. This is a beta test version of TEOS, and it is far safer to just run it like a normal cart from KRIKzz's OS ... you have been warned!

If you find any problems, then it would be better to report them in the "Homebrew Development" section of the "PC Engine Software Bible forum", rather than cluttering up KRIKzz's forum here.

Developers ... please note that TEOS does not currently support uploading HuCard images through the Turbo EverDrive's USB connection!

EDIT: Link updated to beta 4 version which fixes the free space display on empty BRAM slots.

7
Turbo EverDrive / Re: out of stock everywhere, why ?
« on: May 15, 2019, 12:49 AM »
Do you have more details on this somewhere? Sounds very interesting

If you're talking about the OS replacement, you can find the development thread on the PC Engine Software Bible forum.

Here's the current beta of the main screen ...



8
Turbo EverDrive / Re: out of stock everywhere, why ?
« on: May 08, 2019, 11:00 PM »
Well, the current Turbo Everdrive v2 design is nearly 4 years old now ... it's certainly possible that KRIKzz is beginning to find that some components are getting harder to source.

It would be hilarious timing ... I'm getting very close to releasing an open-source replacement OS for the TED2.

9
So I guess there's still no information about whether or not v1 is affected?

Sorry, I've still not gotten-around to finishing-off the test code, I've been busy with a lot of other stuff.

I need to bump it up on my list of priorities.

10
I have to admit I am a little lost.  I have just received the TED 2.4 and have a US Turbo Duo.  How does loading the Super System Card 3.0 "damage" the Turbo Duo?

The information is all detailed in the first few posts in this thread, as is the "solution" in the form of a simple patch to apply to the System Card 3 image.

I'm sorry, but I don't know how to explain it in any simpler terms than it's already been explained ... it's a technical issue, and so it does sort of help to have some understanding of electronics.

BTW ... if you actually the thread, I think that you'll find that I was careful to say "potential damage". Your Turbo Duo isn't going to explode if you don't use the patch, but you're stressing the electronics when there is bus-fighting.

It's totally up to you if you want to risk that just to avoid applying a free patch (that even includes the source code so that you can see exactly what it is doing).

11
Turbo EverDrive / Re: Unusual Error on PC Engine white TED V2.1
« on: January 13, 2016, 05:43 PM »
Agreed ... my TED v2.1 just wouldn't work in some of my PCE systems, but the replacement TED v2.3 is rock-solid.

12
Turbo EverDrive / Re: TED ver1 and ver2
« on: January 13, 2016, 05:41 PM »
AFAIK the "Populous" HuCard is the only game that wasn't supposed to work on the TED v1 that is specifically supported on the TED v2.

You can always get the CD version of "Populous" if you want to run that game with a TED v1.

IMHO, the TED v2 is a huge improvement over the TED v1, and well worth the extra few bucks, but then again, I'm a programmer and so I also recommend getting it with the optional USB addon.

13
Turbo EverDrive / Re: OS Needed for TED v2.4?
« on: January 12, 2016, 05:40 PM »
It's normal ... the TED version 2 hardware is very different to the TED version 1 hardware.

Having the TED OS on the SD card instead of being permanently flashed is just a consequence of the different hardware design.

14
Turbo EverDrive / Re: Running the BIOS for the Super System CD Card
« on: December 05, 2015, 11:04 PM »
In my case , i remove my TED v1 each time before playing CD on my duo-r , but  sometimes i use the US System 3.0 bios to manage my duo memory , i'm not really good in the  Japanese menu ...  ;D
Is it really dangerous for my hardware?  ???

Just running the US System Card 3 on your TED1 so that you can manage the backup-ram before removing the TED1 to play CD games really shouldn't cause any problems.

If you feel worried at all, just run the US System Card 2 instead to manage the backup-ram ... there's definitely no problem at all with that.

FYI ... I don't think of this problem as "dangerous", it's not like your PC Engine is going to catch fire.

But it's definitely not at all "good", and there's no reason for TED2 owners to run the original Super System Card image now that there's a patch to fix the problem.

You probably can't run the patched Super System Card image on you TED1 ... it changes the TED's configuration registers in ways that may well crash the TED1 (it's designed for the TED2).

15
Turbo EverDrive / Re: Running the BIOS for the Super System CD Card
« on: December 02, 2015, 08:56 PM »
Regarding Populous on Duo you don't need to run anything before it.

AFAIK it's looking for RAM in the upper banks of cartridge space ... just where the DUO's SCD RAM is.

I'm not sure how-on-earth you've got it running on a TED1 without unlocking the SCD RAM.


Quote
Regarding the "bus clash", if the RAM (TEDv2 only at thi point) is set to FF it would look like a pull up on the bus so that would not matter and the clash would be immaterial, right?

You'd need a competent electronic engineer to comment on that one. My remembrance of old-tech is that TTL logic worked pretty-much like that, but I'm not at all sure that the PCE's CMOS logic works the same way.

Whatever the answer to that, it's not a problem on the TED2 at this point because there's the patch for the Super System Card.

My investigations showed that KRIKzz didn't seem to be clearing unused cartridge memory to $FF in the TED2, and that you've just got left-over "garbage" in there. That's definitely going to cause a bus-fight without the patch.


Quote
[I don't know if the flash (TEDv1 only) upon erasing/reflashing is set to FF if unused, I am not even sure the erase clears it all (likely it does not)].

An "erase" on the flash memory sets the contents to $FF. But I have no idea how much of the cartridge space KRIKzz erases when the TED OS loads a new cartridge image.


It's a good thing that only the Super CD BIOS is causing troubles. One of the nice things with TED is that you can use any system card with it, including Game Express and CD BIOS v1 for Altered Beast CD.

Agreed, the TED2 is a great piece of hardware, and I highly recommend it to everyone.

Having to run a patched Super System Card image is a minor inconvenience, and is actually a huge benefit to those of us that want to use the extra RAM on a TED2 for translations/homebrew.

Pages: [1] 2 3 4