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

Pages: 1 [2] 3 4 5 6 7 8 9 ... 17
Programming / Re: SymbOS
« on: 2016.November.30. 13:06:48 »
The V9990 is accessed only by these few ports (on the MSX):

; Port defines
G9K_VRAM                EQU     #60     ; R/W
G9K_PALETTE             EQU     #61     ; R/W
G9K_CMD_DATA            EQU     #62     ; R/W
G9K_REG_DATA            EQU     #63     ; R/W
G9K_REG_SELECT          EQU     #64     ; W
G9K_STATUS              EQU     #65     ; R
G9K_INT_FLAG            EQU     #66     ; R/W
G9K_SYS_CTRL            EQU     #67     ; W
G9K_OUTPUT_CTRL         EQU     #6F     ; R/W

So you only need a range of 16 port addresses and can fully use the V9990, which has its own video ram. So maybe it is pretty easy to build an interface for it. SymbOS supports a resolution of up to 1024x212 at 16 colours.
But I agree that a Graphics9000 output wouldn't look like an Enterprise anymore, but it would be a nice project anyway :)
On the MSX it was a little bit different, as it is still looking similiar to the VDP9938 etc. Though even here there was not that much software released for the Graphics9000, a huge part of the apps which run with the G9K are now coming from SymbOS.

Other topics / Re: MSX Computers
« on: 2016.November.30. 12:30:46 »
Are you speaking about this one?

If yes, it is possible :)
(starting at 3:33)

There is a driver for the SD reader, and the SymbOS installer will autodetect it (you will see it in the video).

Programming / Re: SymbOS
« on: 2016.November.29. 22:33:32 »
The reason why the extended partitions pop up: users want to use Sym Commander as file manager for Enterprise partitions.
Then will be good if all partitions can be accessed.
Ok, I agree... Shouldn't be a problem to extend it for the next version!

Programming / Re: SymbOS
« on: 2016.November.29. 16:20:36 »
There is also a "not partitioned" option, probably to format to FAT16/32 within SymbOS. I've not tested if an already created FAT32 partition is detected and used.
Zozo is correct. Today sometimes an MBR is added with one partition, and sometimes there is no MBR, the boot sector of the first partition is directly placed at physical sector 0. In this case you have to select "not partitioned".
I am using the "big" SD card at my EP for all the FAT12 partitions and the micro SD card as a FAT32 device with 32GB for SymbOS only. So I have at least one partition which is shared between EXDOS and SymbOS and one big for all the additional data which can be used in SymbOS (videos etc :) ).
Due to its ability to access larger FAT16 and gigantic FAT32 partitions (up to 2TB in theory) I didn't see the need for supporting extended partitions before (it would made the routine for "activating" a partition a litte bit bigger).

The question are: how many drives (letters) are possible under SymbOS? If also possible up to Z, then only the partition collection routine needed to be extended.
You can use any drive letter between A-Z, but the total number is limited to 8 (again with a nice FAT32 partition this is more than enough :P )

Prodatron say previously it is only possible in the "for extended Enterprise" version, which can be use a different memory map.
That's correct!

Well, with mass-storage solutions now like SD-card, isn't it possible to save the system segment, to the card and restore on exit?
Hm, good idea, maybe the boot loader can do this before starting SymbOS. Then no changes in SymbOS itself are required at all, just a "restore app", which is executed when you quit SymbOS...

This SymAmp are available?
It's currently in Gecos hands :) I just tested his first version from yesterday evening, which he was sending to me.

Programming / Re: SymbOS
« on: 2016.November.28. 16:56:04 »
The structure of the SYMBOS.INI file is described in the attached document (nearly up-to-date), which is included in the developer documentations ( http://www.symbos.org/download.htm#marke1 ).
Maybe you are more speaking about exchangeable mass storage device drivers? This feature is currently only available for the MSX version. Not sure if the IDE interface is still important for the Enterprise. If yes I can plan to make the drivers not fixed but loadable during booting like we have it on the MSX.

Programming / Re: SymbOS
« on: 2016.November.28. 12:55:44 »
The extended desktop modul is using about 37K (16K buffer for desktop icons, startmenu entries, widget properties, 11K code etc.):
Additional 64K would be enough :)

Programming / Re: SymbOS
« on: 2016.November.28. 12:32:35 »
Yes, it's the "load SymbOS extensions" option in the Control Panel -> System -> General tab, see here:

Programming / Re: SymbOS
« on: 2016.November.28. 00:07:48 »
I love it and I wait for it very much! :-)

Thanks! :) The current preview is probably very close to the final release of SymbOS EP 3.0. I am trying to do the official release still in 2016 (around Xmass).
The website has been updated as well:
Some of the new sections are not finished, but at least the application area is now database driven and up-to-date:

Programming / Re: SymbOS
« on: 2016.November.27. 21:06:10 »
But Prodatron still has to extend the resolution to the max admited.
Yes, that's not planned for 3.0, as it requires some more work and will also split the EP port into two branches (normal and "power" version ;) ).

Programming / Re: SymbOS
« on: 2016.November.27. 20:43:36 »
Oh, seems that I didn't write about this here before (only mentioned the new Widgets in one post?).

The "extended desktop" is an optional module (working like an own app), which can be loaded during booting. It is replacing the desktop and startmenu management of SymbOS with some enhanced features.
- startmenu with nearly unlimited entries and nested submenus
- desktop with nearly unlimited icons; icon handling like in Win9x with auto alignment, property forms etc.
- widget support; you can place little widget apps directly onto the desktop (no own forms but they are part of the desktop itself); these could do things like the widgets you know from your smartphone (clock, cpu meter, weather widget w.i.p [erm yes, EP still needs an ethernet hardware - Bruce? :) ])

Here are some screenshots:

16638-0 16640-1 16644-2 16646-3 16648-4 16650-5 16652-6 16654-7 16656-8 16658-9 16660-10 16662-11

Not sure if I already posted something about the new help browser for SymbOS here:
Edo and me started some HLP files for most of the existing apps, though they are still not completed. The new help file browser is quite similiar to the old one for Win9x with chapters, different font styles etc.

Hope you will like some of the new stuff.

Programming / Re: SymbOS
« on: 2016.November.27. 18:14:21 »
After playing around with different values it seems, that it's working now for all types of CPU clocks. During booting SymbOS is measuring the CPU speed and prepares the wait-values for the EnterMice routines. It should use 3,3,3,... for 4MHz and 9,9,9,... for 10MHz machines (and something inbetween for 6 and 7,5MHz). Because of the automatic generation of the values some waits may be a little bit too long, but at least for 10MHz I really had to use 9,9,9,... all the time, and currently I am just glad that it's working now.

* SymbOS-EP.zip (366.31 kB - downloaded 325 times.)

Here is a DSK with the actual build of SymbOS 3.0. It is using the Extended Desktop, so it won't fully boot on machines with 128K only (just delete the SYMBOS.INI if you have 128K only).


It seems to run fine on the Enterprise!
For the EP specific port of 3.0 there is only one item left on my todo list:
- debugging the FDC routines

Programming / Re: SymbOS
« on: 2016.November.26. 21:46:17 »
Good idea, thanks for the hint Geco! That's how I did it for the old Boxsoft driver, will try it for the EnterMice driver now as well!
A static 5/8 delay didn't work for all kind of CPU speeds right now (or maybe I missed something).

Programming / Re: SymbOS
« on: 2016.November.26. 21:32:02 »
Both buttons are working now fine, but I have problems with the "waits" for faster machines.
IIRC my Enterprise 128 upgraded by Zozo is working at 4, 6, 7.5 and 10MHz. If I use the timing of Bruce routine...
...the pointer is going crazy at everthing > 4MHz.

I was already experimenting with different "wait" values. The strange thing is:
- everything is working at 4MHz
- some "waits" are working only at 4 and 10MHz but not for 6 and 7,5
- some are working for 4 and 6 OR (?) 7,5, but not for the other two

Anyway it's fantastic to have a real and full working mouse at the Enterprise inclusing the wheel! :)

PS: Zozo, you are right regarding the PS/2 mouse :)

Programming / Re: SymbOS
« on: 2016.November.25. 18:52:23 »
Thanks for the hint, Zozo! Hope that's the problem.

Programming / Re: SymbOS
« on: 2016.November.25. 17:16:54 »
With Gflorez help I was able to update the mouse routines for EnterMice support today! :)
Thanks so much to Pear for this great hardware, to Istvan-V for fully emulating it in the fantastic EP128Emu and to Gflorez for your help!

The mouse wheel is already working fine. I will now add support for the right mouse button and then publish a preview here.

It seems, that my USB mouse (+adapter) isn't working with my EnterMice hardware on my real EP, its LED stays dark. I guess I have to buy a real PS/2 mouse (I wonder where I leave my old one...).

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