On Sat, 28 Nov 1998, Jun-Sung Kim wrote:
> Date: Sat, 28 Nov 1998 10:33:42 +0900 (KST)
> From: Jun-Sung Kim <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: My MSX project + protect mode
>
>
> Hi,
>
> Lately abou
> Make it possible to use segments. What I mean is you can set some register
> outside the cpu on a value rg and if an address ad is asked by the cpu,
> the address that is actually read out is ad+mf*rg, where mf is a
> multiplying factor, prefferibly smaller than 64 (use a power of 2 of
> course
Shevek wrote:
>If you want to make a new memory-configuration, and it should be
>multitasking (please, make it linux-like and not windows-like),
I agree with this.
>I have a
>tip for you that most pc-programmers will not agree with:
>Make it possible to use segments.
N!! Not segments!!! :
Hi All
I do not answer on Your letters. Because they have no any questions. Indeed
I attentively read them.
Thank you very mutch For help :-)
Valery
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]"
>I have a slightly different idea. Allow write protect option for a part of
>the RAM. Just like turbo R BIOS in DRAM, or ESE-SCC in ROM mode.
>
Can You Write me about details?
Valery
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "
Hi
> There are several I/O controller chips for PC. I consider to use
>PC87309 of National Semiconductor. It includes keyboard/mouse
>controller, floppy disk controller, parallel and serial ports.
>
How about hardware compatibility. PC87.. have own i/o adress space.
KBD is it problem too. RS
Hi,
Lately about the protected mode...
If you want to implement it, minimize it.
The reason that I like MSX, is the full controllability. MSX is a
PERSONAL Computer, so all results are responsible to the user.
Well, it may be also good to prevent the important system area
being crushed in a
At 10:35 AM 11/25/98 +0600, you wrote:
>As possible do protected mode?
>
>Why? For raising system reliability.
>
>Processor Must have 2 modes system and user. Bit "super"
>In the field of memories is conducted place which is only read in mode
>"user".
>If processor causes function of system that
Hi,
> If you want to implement it, minimize it.
>The reason that I like MSX, is the full controllability. MSX is a
>PERSONAL Computer, so all results are responsible to the user.
I want to make protect mode not for user. It will be for crash-programm.
User can free to change "super" bit.
>
>
Hi MSXers,
>
> > Do you mean that 00-3F can be used both for linear addressing
> >and memory mapping (MSX2 standard)?
>
>
> Yes
>
> Do You think on other?
>
I, myself, thought to make two separate memories.
When access below 64KB space, memory module A(4MB, memory mapper,
MSX2 sta
On Tue, 1 Dec 1998, Patriek Lesparre wrote:
> Date: Tue, 01 Dec 1998 04:54:43 +0100
> From: Patriek Lesparre <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: My MSX project + protect mode
>
> Shevek wrote:
> >If you want t
At 08:46 PM 11/26/98 +0600, you wrote:
>>I have a slightly different idea. Allow write protect option for a part of
>>the RAM. Just like turbo R BIOS in DRAM, or ESE-SCC in ROM mode.
>
>Can You Write me about details?
Using write protect:
Let's say you have a Z380 system with 4MB RAM, at address
Hi
As possible do protected mode?
Why? For raising system reliability.
Processor Must have 2 modes system and user. Bit "super"
In the field of memories is conducted place which is only read in mode
"user".
If processor causes function of system that super=on. Access To registers of
governing p
Hi
As possible do protected mode?
Why? For raising system reliability.
Processor Must have 2 modes system and user. Bit "super"
In the field of memories is conducted place which is only read in mode
"user".
If processor causes function of system that super=on. Access To registers of
governing p
Hi,
>
> Hi
> I wrote I want build MSX-3 ( non ASCII standart )
> I wrote FPGA-Mem memory controller for my MSX3 computer. It take
> EPM7128SLC84. I writing other FPGA-IO now.
>
> FPGA-Mem specification:
> Using one or two 16Mbit 60-nc DRAM 1MbX16Bits
>
> Z380 Memory map
>
> 00-00
Hi,
> What is the EXTENDED MSX SLOT and what's the difference between 40-
>and 80- ?
>
It is different signals /SLTSL0 and /SLTSL1 ( as beside MSX )
connected to different connectors.
To avoid decoder of address on affiliated card
> Also why INTERNAL MSX SLOT is needed?
That which b
Hi,
Who know about MSX-hardware mail list?. If such be
There is in view of hardware development.
It is Correct have on slot-connector the pins /TREFA,/TREFC,/TREFR ?
/TREFA Timing Reference A (output, active Low, tri-state).
This timing reference signal goes Low at the end of T2 and
returns Hi
Hi
I wrote I want build MSX-3 ( non ASCII standart )
I wrote FPGA-Mem memory controller for my MSX3 computer. It take
EPM7128SLC84. I writing other FPGA-IO now.
FPGA-Mem specification:
Using one or two 16Mbit 60-nc DRAM 1MbX16Bits
Z380 Memory map
00-00MSX MEMORY
01-3FDR
-Mensaje original-
De: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Enviado el: lunes 30 de noviembre de 1998 12:53
Para: [EMAIL PROTECTED]
Asunto: Re: My MSX project + protect mode
> Make it possible to use segments. What I mean is you can set some register
> outside t
19 matches
Mail list logo
