Welcome, Guest. Please login or register.


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 - gflorez

Pages: [1] 2 3 4 5 6 7 8 ... 188
1
Hardware / Re: Questions about SymbiFace3
« on: Yesterday at 20:49 »
Ah ok, now I see. You have to create a RomBank dir on the second screen(press "m" on the first screen to enter the banks screen).

2
Hardware / Re: Questions about SymbiFace3
« on: Yesterday at 20:46 »
I don't see the names of the ROMs.
(startup bank: 0, Actual bank: 0)

These are test names that I have put in my EP.... put them you also on your EP if you like them... or better put your own names.

Remember to remove Rom definitions on the INI file if you use Rombanks at the same segments.

To define Roms, first you have to store the original Roms on a directory defined by you, for example on the root of the USB(drive 1). Then search the Roms on the ROM Manager program.

3
Érdekes volt tudni, hogy kinek volt SF3 Oroszországban...

-----

I was intrigued to know who had SF3 in Russia....

-----

Estaba intrigado por saber quien tenía SF3 en Rusia....

4
I have tried the English membrane(It seems it is no more being offered on the Sellmyretro web page) and the Hungarian one, being the second a lot better and cheaper. 

5
I know(or at least I imagine) that it gives you a lot of work, but still it seems magic for me how you are able to make these replicas with that marvellous perfection.

Thanks for attempting to accomplish this dream.

6
Luxurious!

I can see a crack on the case of your computer near the joystick, the very same on my two EPs... The joystick is the  weakest zone on the machine, and the most used.


7
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.21. 11:33:09 »
The Rom Manager is very easy to manage, but maybe I must insert here some hints.



As you can see, its screen has a two columns approach with a cursor(moved by the internal joystick), with the current boot bank and the current edited bank indicated on the upper side, and some key options on the bottom side.

As I have said before, it is important to save all the needed Roms on a directory on the SF3 Sd, let's say, "Roms", for example. This program doesn't have a file manager for this, so we must know previously the path of the Rom file.

On the image I have some Roms already introduced, but you can go to an empty segment and press the "u" key. Avoid selecting a segment adjacent to one Rom bigger than 16KB, always leave enough space for them.



On other screen we will be asked about the SF3 drive, and then the path. The original Rom will remain untouched, but a copy of the file will be created on the actual Rombank directory. If the file is not found, the program exits showing us the error. This can be modified on a future.

The other options of the main screen are very descriptive of what they do, "e" will exit the program and "r" will allow us to modify or add text to the Rom description.

The "b" option is important, because it will lead us to a similar screen showing us the list of Rombanks actually in use.



The most relevant keys here are Enter, that will set the cursor Rombank as the editable one(and will exit from here to the main screen), and the "£" key("#" on German keyboards), that will set the cursor Rombank as the Boot one. Here you can also create a new Rombank or modify its name. Observe that a delete Rombank option has been avoided, but it can easily  made erasing the complete directory.

8
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.20. 12:06:21 »
Now I ask myself: Has the SF3 more versatile ways to inject Roms?

Yes, they are named Rombanks.

Imagine that you need to have two or more Rom arrangements. I mean, various Rom configurations at boot, selectable at the touch of a button.

Do we Enterprise users need that? Seriously, I think that EXOS  allows a huge amount of Roms to be integrated all at the same time on the system. But this doesn't happens on a CPC. If you install more than 16x16K Roms the system hangs, due to not have place for the stack, because every Rom needs to add a descriptor.

The solution: On a CPC you can place more, up to 128 Roms if memory provided, but only the first 16 will be on the system Rom list.

This situation leads us to the Rombank method, that we have inherited from the CPC SF3 development. The need to have at hand a lot of Roms integrated on the system.

The only advantage this system gives us is that is a lot faster than the usual INI Rom definitions, but it needs to leave the Rom without its real name.

The implementation of this method works as this: just before the INI file execution, the SF3 searches on its SD for a directory named BANKXXX on the path SD:EP/ROMTABLE/.   XXX is a number from 000 to 999. If found, the Rom files found on it will be injected on memory. If not found, the normal procedure, searching for the INI file is continued.

Where are the files injected?

The Rom files have this name format: ROMXXX.BIN, with an associated descriptor file ROMXXX.TXT to store the name of the file. XXX is the target segment number on decimal. On the same BANKXXX directory an additional file can be found:  BANKNAME.TXT , that contains the name of the Rombank.

Once injected the selected Rombank, the searching for the INI file is executed, so it can be that the previous Rom configuration could be thrashed by the INI's Rom or Ram definitions. Is the user who must control how the boot configuration is executed.

Usually the default Rombank is 000, but the SF3 has commands to change it, or you can press the Right button on the OLED screen to select other bank of the present Rombanks.

All that rename, create files and DIRs can be made with a simple Basic program, attached to this message. The only rule is to have the Roms we want to put on the Rombanks on a DIR on the SF3 SD(or the USB), to be find by the program.

On the Rom Manager program, transcribed from the CPC Basic program, the segment positions of the Roms are from 96-127 decimal, 60-7F hexadecimal, but on the Enterprise you can put by hand other Roms on other segment positions.

Remember that this arrangement will only work on Zozo's modified EXOS Roms, on the stock EXOS Roms only the 60h and 70h(96 and 112 decimal) segments will be searched for Roms.

Once the Enterprise+SF3 booted, you will see something like this:



The second line means that the left button below the OLED screen re-connects Wifi., the middle button is still not defined, and the right one points to Rombank 0. I have already defined it, and some others more for tests. If you press the button it will lead you to a dialogue to select other rombank, only if you have defined it.

Remember, on the boot sequence, first goes the Rombank, and then the INI itself, so the later has priority over the first.

9
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.17. 15:54:42 »
Now only remain the explanation about the SF3 sound modes:

Code: [Select]
AUDIO=  SYMAMP
This is the default option, MP3A. You can put here other Sound mode(I will explain them later), but better not, because some programs expect this mode at start.

If you deactivate it(Asterisk) or directly you remove the lin, the SF3 will not sound, but it will also lose the USB "disk commands", because these are based on AT commands, that are on the software sound module.

Why it is named SYMAMP?, because the sound module on the SF3 is based on the SE-ONE(TMTLogic) MP3 MSX cartridge, a clone of the Sunrise Mp3 cartridge. The classic cartridge is supported on SymAmp(SymbOS) since its creation on 2013, so that was the reason on making the SE-ONE and the SF3 compatibles with that hardware, to have an immediate use on existing software.

10
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.17. 11:20:02 »
Let's continue with the explanation about the INI file.

As you can see on the Rom definitions, you could put your Roms on a directory or on a complex path on the SF3 SD, not on the root of the SD card like I have done.

You surely have seen this line on the Rom definition section on the file:

Code: [Select]
*ROM[#XX] =HTTP:www.tmtlogic.com/cyrus.rom
Yes, you even can download a file from a remote web page and also from another place on your house...

Try this line on your Enterprise, remove the asterisk and select the segment where you want to inject the chess game.

The SF3 will try to connect to WIFI even if you have the "WIFI_CONNECT" command disabled.

About downloading files from the home net, better I will wait with the explanations until making some tests to know better how it works.

11
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.14. 21:58:53 »
I mean, 16KB resolution only for the cartridge zone, 04-07. The rest of memory range is correct with 64KB resolution.

12
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.14. 21:14:04 »
I enjoy doing this, it is not an effort.

But not all is enjoyment... for example, I have introduced a very BIG ERROR when I put the range 05-07h as an example to use the max. memory possible on a stock UK EP128.

Due to the size of the CPLD used on the SF3, the memory addressing on the Enterprise approach has only one limitation: every 4 segments(64Kb) can only be Ram or Rom. There is a resolution of 64KB for selecting Ram or Rom.

This means that I can not take the spare 02, 03, 05, 06 and 07 segments to put Ram there, I only can put Rom on 02 and 03(the modified EXOS Roms from Zozo have 64KB), or I can select to put 64kB Ram on the cartridge(03-07), only if I don't put any Rom there.

Then, on a 16 segments row, for example 20-2F, I have freedom to put all Ram or Rom on chunks 20-23, 24-27, 28-2B, 2C-2F.

Is it enough freedom? I think yes.

But, just because SF3 is eminently software, I am going to ask Hans if the cartridge zone can be defined differently, a special zone, to be able to emulate the hybrid classic cartridges that had Ram and Rom on them.


I apologise for the confusion I have introduced...

I will fix the past explanations.

13
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.14. 15:04:22 »
A lot of juicy questions...

First, the SF3 mouse implementation  is not compatible with all USB mice, but this is because there are thousands of mice implementations on PC. When you find a compatible mouse it works perfect.

You can use the SF3 mouse with programs that use the Mouse Driver, I added SF3 mode long ago. These are Paintbox, EGI and Basic. Still not on SymbOS, sorry. Prodatron has to add compatibility, like he has done on the CPC SymbOS port.

The games or apps that use directly the EnterMice hardware will not work, sorry, they must be adapted. I will try them on time.

The RTC inside the SF3 will be included by Zozo on a future on his Zozotools, so it will happen, and I hope the same with the SF3 USB and SD.

About TMTNet, I can say just now that TMTnet is incompatible with SymbOS-net, but I am sure that the SF3 will work with SymbOS-net when Prodatron make a driver for the wifi module on it. On the other side, TMTnet is totally possible as an app on SymbOS.

SymAmp is oriented to files, mode MP3A on SF3, while the Basic program SEPLAY2 is remote playing oriented, mode MP3B on SF3. The second one is better, because it doesn't stress the Z80 sending the song data to the Mp3 chip, it is the SF3 itself who manages the file and the data.

But we still don't have an EXDOS driver for the USB and SD on the SF3, so we only can use SymAmp playing MP3A from the SD-cartridge. And about SymAmp playing remotely the Mp3 files on SF3(MP3B), it would need very deep rewriting, surely.

I see easier to write a new SEPLAY app on QUIGS or machine code on EXOS. But all can be because we have the SymAmp assembly source.

I am almost sure that once having an EXDOS driver for the USB+SD we will have it also on SymbOS, because it takes its drive list from EXDOS. And SymbOS is already FAT16/32 compatible, so it will read partitions formatted FAT16 with EXDOS 3.0(Bruce).

14
Wanted / Re: 1MB RAM expansion with built in Exos 2.4
« on: 2020.July.14. 11:13:40 »
Ok, I could, probably on a future, produce a copy of Saint's Ram expansion... May be some user would need it, but not John Fante, who already owns a SF3.

On the other side, I don't think that the internal memory shown on the picture(Hungarian SMD type) had place for the EXOS.Rom.

I don't see the point on putting the EXOS Rom on the internal expansion memory. Once you open the EP, it is very easy to remove the original Rom(It always comes in socket) and plug a 64KB EPROM. It only needs to solder an additional address bus cable to expand the addressing range from 00-01 segments to 00-03 segments. There is a thread on how to do it.

Zozo or I, both can provide the necessary 64KB programmed EPROM, but it is a lot easier: a) buy blank 64KB EPROMS on a components shop, that probably has a programming service once the Rom file is provided, or b) buy the blank EPROMS and order on China a cheap chip programmer.

About adding (a lot of) memory to your Enterprise with a SF3, please read the thread "Questions about SymbiFace3". Also, it is the perfect place to solve your SF3 doubts.

It is also possible, with the SF3, to inject the EXOS Rom on an Enterprise without the internal Rom on its socket. It needs to enable the ROMEXOS_ENA=ON command on the INI file. This option is intended more for hardware fixing purposes, not for a daily use, because then the Enterprise can't start without the SF3 connected.

John, can you show the damage on your internal memory expansion?, maybe it could be fixed.



 


15
Hardware / Re: Questions about SymbiFace3
« on: 2020.July.13. 10:41:50 »
Sorry, I was very lazy with files... Soon I will share others that only I have.

SF3Boot.Rom can be on any segment, but for standardisation, and because one of the Basic programs manages Roms there, better put it on the 60h segment, and additional user Roms on 61-6Fh. If you still need more Rom space, use the 70-7Fh zone also. Check that the zone don't clash with your memory expansions.

Don't worry if, accidentally, some SF3 Rams/Roms clash with other internal or external memory(Ram/Rom) expansions, they will be mixed , it is not harmful, only will produce malfunction. Is the user who has to be careful with memory definitions.

Pages: [1] 2 3 4 5 6 7 8 ... 188