At 12:25 AM 7/20/99 +0200, you wrote:
>I have used the uzix demo in sanyo wavy 70 fd2 and all its OK.
But the current version doesn't access the FDC directly. So although it's
nice to know it runs on a Wavy, it doesn't say anything about the FDC.
Bye,
Maarten
MSX Mailingl
Hi all
I have used the uzix demo in sanyo wavy 70 fd2 and all its OK.
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~w
] On Fri, 16 Jul 1999, Alex Wulms wrote:
]
] > ] Right! Thanks. Could you send us an overview about Wavy FDC?
] > Wavy contains the TC8566AF, just like the MSX turbo R. A couple of weeks ago
] > I sent the TC8566AF datasheets to somebody in Brazil. I don't remember his
] > name at this moment.
On Fri, 16 Jul 1999, Alex Wulms wrote:
> ] Right! Thanks. Could you send us an overview about Wavy FDC?
> Wavy contains the TC8566AF, just like the MSX turbo R. A couple of weeks ago
> I sent the TC8566AF datasheets to somebody in Brazil. I don't remember his
> name at this moment.
That's me!
] On Thu, 15 Jul 1999, Alex Wulms wrote:
]
] > ] Is Wavy supported by FastCopy?
] > Yes. See my homepage for the drivers.
]
] Right! Thanks. Could you send us an overview about Wavy FDC?
Wavy contains the TC8566AF, just like the MSX turbo R. A couple of weeks ago
I sent the TC8566AF datasheets
On Thu, 15 Jul 1999, Alex Wulms wrote:
> ] Is Wavy supported by FastCopy?
> Yes. See my homepage for the drivers.
Right! Thanks. Could you send us an overview about Wavy FDC?
Greetings from Brazil!
-
Marco Antonio Simon Dal Poz
] Is Wavy supported by FastCopy?
Yes. See my homepage for the drivers.
Kind regards,
Alex Wulms
--
Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever
See my homepage for info on the *** XSA *** format
http://www.inter.nl.net/users/A.P.Wulms
MSX Mailinglist. To unsubscribe, send an
At 03:39 PM 7/14/99 -0300, you wrote:
>> About incompatibility, that can be avoided by making sure there are
>> drivers
>> for every FDC ever used for MSX. I know only 4 different ones:
>> Philips/SONY
>> (mem), turbo R (mem), Sanyo Wavy (IO), Brazilian FDCs (IO). Maybe there
>> are more, but the
On Sun, 11 Jul 1999, Alex Wulms wrote:
> ] About incompatibility, that can be avoided by making sure there are drivers
> ] for every FDC ever used for MSX. I know only 4 different ones: Philips/SONY
> ] (mem), turbo R (mem), Sanyo Wavy (IO), Brazilian FDCs (IO). Maybe there are
> ] more, but the
On Sun, 11 Jul 1999, Maarten ter Huurne wrote:
> About incompatibility, that can be avoided by making sure there are drivers
> for every FDC ever used for MSX. I know only 4 different ones: Philips/SONY
> (mem), turbo R (mem), Sanyo Wavy (IO), Brazilian FDCs (IO). Maybe there are
> more, but the
Jon,
> > Remember that UZIX doesn' uses DOS. It acesses peripherals
> > directly (using their ROM, if available).
> well, that's the problem: if you want to use the diskrom, you should keep
> the diskromvariables in page 3 and not overwrite them with zeroes!
> It is no problem to ove
On Tue, 13 Jul 1999, Adriano Camargo Rodrigues da Cunha wrote:
>
> Jon,
>
> > > Well... What I do is clear hooks and fill the area D000h-F000h
> > > with zeros...
> > hmmm... seems dangerous to me: some hardware drivers can be installed in
> > this area at startup. (example: wo
Jon,
> > Well... What I do is clear hooks and fill the area D000h-F000h
> > with zeros...
> hmmm... seems dangerous to me: some hardware drivers can be installed in
> this area at startup. (example: workspace of diskroms). MSX system area
> is from #F380...#. Below that area
] About incompatibility, that can be avoided by making sure there are drivers
] for every FDC ever used for MSX. I know only 4 different ones: Philips/SONY
] (mem), turbo R (mem), Sanyo Wavy (IO), Brazilian FDCs (IO). Maybe there are
] more, but the number is managable.
Sanyo Wavy uses mem as well
At 06:49 PM 7/10/99 +0200, you wrote:
>> Another option: use UZIX drivers for every hardware device.
>> For example FastCopy also uses drivers to support different types of FDCs.
>
>MAARTEN!!!
>
>Are you really suggesting this?
>If something will result in incompatibility...
No, I haven't gone m
> >hmmm... seems dangerous to me: some hardware drivers can be installed in
> >this area at startup. (example: workspace of diskroms). MSX system area
> >is from #F380...#. Below that area, the DOS kernel area; from #F1C9
> >to #F37F for the DOS2.x kernel (probably the same for DOS1 kernel).
>
Maarten ter Huurne wrote:
>
> >hmmm... seems dangerous to me: some hardware drivers can be installed in
> >this area at startup. (example: workspace of diskroms). MSX system area
> >is from #F380...#. Below that area, the DOS kernel area; from #F1C9
> >to #F37F for the DOS2.x kernel (probably
At 11:40 PM 7/8/99 +0200, Jon wrote:
>hmmm... seems dangerous to me: some hardware drivers can be installed in
>this area at startup. (example: workspace of diskroms). MSX system area
>is from #F380...#. Below that area, the DOS kernel area; from #F1C9
>to #F37F for the DOS2.x kernel (probabl
Adriano Camargo Rodrigues da Cunha wrote:
>
> > I bet that Uzix is overwritting the DOS2 mapper area. Why you don't try
> > to detect and
> > kill DOS2 during boot ? (Maybe the problem has notting to do with this
> > ... But I said anyway)
>
> Well... What I do is clear hooks and fil
]
] Alex,
]
] > ] With DOS2 cartridges, DOS1 bootsectors (yes, UZIX disk bootsector is DOS1)
] > ] also enable BDOS2???
] > ] If the answer is yes, HOW can I disable DOS2?
] > Answer is yes.
] > Answer to second question is: NOT. Though, there are three different
] > solutions to follow
> I bet that Uzix is overwritting the DOS2 mapper area. Why you don't try
> to detect and
> kill DOS2 during boot ? (Maybe the problem has notting to do with this
> ... But I said anyway)
Well... What I do is clear hooks and fill the area D000h-F000h
with zeros... But when I do it, I a
Adriano Camargo Rodrigues da Cunha wrote:
>
> The problem happens before it...
> A UZIX disk contains a DOS1 bootsector.
> Based on Duddu report, even the bootsector isn't executed
> correctly.
> I don't use DOS2 mapper routines, I have my own interrupt handler,
>
Alex,
> ] With DOS2 cartridges, DOS1 bootsectors (yes, UZIX disk bootsector is DOS1)
> ] also enable BDOS2???
> ] If the answer is yes, HOW can I disable DOS2?
> Answer is yes.
> Answer to second question is: NOT. Though, there are three different
> solutions to follow:
> 1) Use the
] With DOS2 cartridges, DOS1 bootsectors (yes, UZIX disk bootsector is DOS1)
] also enable BDOS2???
] If the answer is yes, HOW can I disable DOS2?
Answer is yes.
Answer to second question is: NOT. Though, there are three different
solutions to follow:
1) Use the DOS2 mapper routines if DO
Laurens,
> > Anybody knows if a DOS2 cartridge have different initialization
> > procedure than TR DOS2 ROM?
> Ahhh... well, that explains it. UZIX does NOT work with Dos2. On an MSX
> turboR however, Dos2 is only enabled if the inserted disk is Dos2-formatted.
> If any other format (inc
> Really, I don't know. As I said, in my TR (that the DOS2 ROM can't
> be disabled), UZIX boots right.
> Anybody knows if a DOS2 cartridge have different initialization
> procedure than TR DOS2 ROM?
Ahhh... well, that explains it. UZIX does NOT work with Dos2. On an MSX
turboR however, Dos2 is on
> Hey, Manuel, logging as a user and, at prompt, doing another
> login, works. And you can see all processes running. Try it (but use more
> than 128k RAM).
I would like to use more than 128kB RAM: on my Sony HB-F700D (256kB Mapper in
slot 3-3), but as you know, UZIX crashes on it... Alread
Good work ;-)
Bye,
Stefano
-Messaggio Originale-
Da: Adriano Camargo Rodrigues da Cunha <[EMAIL PROTECTED]>
A: <[EMAIL PROTECTED]>
Data invio: martedì 6 luglio 1999 19.06
Oggetto: Re: UZIX & DOS2
>
> Duddu,
>
> > Without Dos2 everything goes right ...
Duddu,
> Without Dos2 everything goes right ... that was the problem ? But why is
> there this problem ?
Really, I don't know. As I said, in my TR (that the DOS2 ROM can't
be disabled), UZIX boots right.
Anybody knows if a DOS2 cartridge have different initialization
pro
29 matches
Mail list logo
