Re: IDE driver documentation
On Sat, 7 Nov 1998, Egor Voznessenski wrote: I _DO_ have complete, working DOS1 DISKROM source code, I even did huge modifications to it to make it more suitable for HDD interfaceing (eg FAT is not held in memory but is loaded from disk when necessary). I even located and corrected a bug of the original code (it is probably present in ALL diskroms out there, but luckily it needs a very special configuration to show up) There have been few quys, who have been telling about bugs in MSX ROM. (This bug, MSX tR disk drive shutdown bug, MSX1 paint routine bug etc.) I think, that it would be nice, if we could collect this information together somewhere with descriptions about actions, when this bug appears, where is the probblem and how this routine should be done. It is very anonying, when you do some proggram, that does not work and after months you find out, that a probblem was in ROM routines, that you used. About this source code... Can you upload it to funet or can you put it to your www-page? There seems to be many people, who wants it. BTW does anybody have assemby source for working paint routine ? ,_. _=_=_=_=!_MSX_!=_=_=_=_=_=_=_=_, ! A1ST ~--- - I ( o o o o o o )i /`, / .::;::; ., / :::.:.:.::::!. -=- `, ~== NYYRIKKI : [EMAIL PROTECTED] 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/~wiebe/mailinglist/)
Re: IDE driver documentation
hi all,
Could you implement 8 drives too??? The system (DOS) can handle 254 drives
exept for one function. And this function is barely used. So drives A-Z
should be possible...
From where did you get the information about the 254 drives?
Have you disassembled the DOS(2) kernel
By the way, this non-supporting function is a Dos1-function call which
returns a value of which every bit corresponds to a drive (1=available,
0=not available). But even this function can be expanded to more drives. I
read in the official documentation that this is returned in HL and not only
in L. Therefor, it is possible to use 16 drives with this function!!! At the
moment H is returned 0 always, but it is preserved for more drives. So it
should be possible to return the next 8 drives here. And the last 10
drives... Well, those can't be detected using this function. A new function
has to be made for support of these.
This is what the manual says about it:
---
3.25 GET LOGIN VECTOR (18H)
Parameters:C = 18H (_LOGIN)
Results: HL = Login Vector
This function returns a bit set in HL for each drive which is available,
bit-0 of L corresponding to drive "A:". Up to eight drives ("A:" to "H:")
are supported by the system currently, so register H will usually be zero on
return.
---
The rest of the functions use a drive-number with the value 0 corresponding
to the default drive and values 1-255 corresponding to the rest of the
drives. Other functions use 0="A:", 1="B:" etc. Depends on the type of the
function call.
I think it won't be a great problem to expand driveletters to 16. But
anyway, this requires disassembly of the whole DOS2 kernel :-(
~Grauw "I have a feeling that this isn't the thing he's programming and
talking about..."
No, he's talking about 32MB partitions on IDE-harddisks. I've mailed him
a couple of times; but as far as I've understand his work will lead to a
dead end: he is working on lowlevel sector read/write routines for IDE,
but these are already implemented in the IDE-bios of the interface of
course. He hasn't really thought of the fact what should be done next
after you can read/write sectors.
In my opinion -if you want to work with files- you'll have to modify DOS2
kernel routines (sectornumbers#). But he doesn't want to use DOS2. So
don't expect real partitions 32MB :-(
Let's start the 32MB partition discussion again!
Greetz,
Jon
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/~wiebe/mailinglist/)
Re: IDE driver documentation
On Tue, 27 Oct 1998 08:46:45, Ricardo Jurczyk Pinheiro wrote: Some of you already knew that I'm writing a new IDE driver that would make possible accessing 32Mb partitions on MSX-DOS(2) via an external shell (maybe a Norton Commander-like) or maybe patching BDOS entry point. Buahhh (Crying) I wanna this driver 4 SCSI! Don't look so far. My driver is not yet finished, it's still in its earliest development stages and I don't even know if I will ever be able to release an 'stable' version of it. But you can bet I'm working on it. [EMAIL PROTECTED] http://usuarios.intercom.es/ag0ny 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/~wiebe/mailinglist/)
Re: IDE driver documentation
On Sun, 1 Nov 1998, Laurens Holst wrote: Could you implement 8 drives too??? The system (DOS) can handle 254 drives exept for one function. And this function is barely used. So drives A-Z should be possible... I know about this, but why don't you wait until I have a working set of routines before asking for new features? The only thing my routines do (now) is reading sectors, and nothing more. Wait for it to be finished (if it ever gets finished). By the way, this non-supporting function is a Dos1-function call which returns a value of which every bit corresponds to a drive (1=available, 0=not available). But even this function can be expanded to more drives. I I know, but I'm not interested at all in modifying MSX-DOS(2). Just wait. 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/~wiebe/mailinglist/)
Re: IDE driver documentation
shevek wrote: Don't you guys have a disassembler? I have, but I don't want only the instructions with real adress or values in the source code, I want a source code with oficial "labels", like BIOS's routines entry points, entry points in HOOKs, etc.. I disassembled the whole BIOS+BASIC from my MSX Turbo R GT using a program sent to me by a friend, and now I'm changing the real adress, like #, to an oficial LABEL, like CHKRAM. It's take time. Best Regards. Alex Mitsio Sato 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Egor Voznessenski wrote: I _DO_ have complete, working DOS1 DISKROM source code, I even did huge modifications to it to make it more suitable for HDD Considering the amount of interest in this piece of work, you better up it to funet :-) The file is being uploaded (ATAROM.ZIP) But the most fresh copies of my software are ofcourse on my server: http://cisip.sonnet.ru/MSX -- EV [MSX Maniac][Pendorian Wannabe][Tubed Audiophile] [email:[EMAIL PROTECTED]] [www.glasnet.ru/~msxegor] 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/~wiebe/mailinglist/)
Re: IDE driver documentation
I'm not a good programmer, i'm doing something in basic and nothing more. But i have a question: Why is so difficult to disassemble the dos2 kernel? We can dump the bios to use it with an emulator but we can't look into it? why? CIAO !!! Maurizio x Morandi a.k.a MxM Softworks on Msx $ IN MSX WE TRUST $ 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Alex Mitsio Sato escreveu: Ooo! You have the DISKROM source code! Could you please send a copy to me through e-mail? With this source code, can I build a faster (ou more optimized) version of the DISKROM? Hi! Could you send me a copy of this source code? I want it too. I want the source code of all about MSX ROMs like BIOS, BASIC, DISKROM, etc. If anybody have it, please, send to my email. Send it to my e-mail too, i would like to study it. thanks. []s Mauricio Braga. 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/~wiebe/mailinglist/)
Re: IDE driver documentation
:I think it won't be a great problem to expand driveletters to 16. But :anyway, this requires disassembly of the whole DOS2 kernel :-( I was talking about expanding to 36... Anyway, about the FAT16 and 8 drives; It is true that if you have FAT16 you probably won't need 8+-drives, but I think this is very easy to implement. And if you make FAT16 this should _really_ be easy and a nice step-in-between. For I don't want to reformat my complete HD but I'd like to use more than those 8 drives. ~Grauw 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Maurizio wrote: I'm not a good programmer, i'm doing something in basic and nothing more. But i have a question: Why is so difficult to disassemble the dos2 kernel? We can dump the bios to use it with an emulator but we can't look into it? why? It's easy to disassemble and read. Understanding is the hard part. In assembly, all the commands are so simple, that without the authors comment, it's very hard to understand. I myself have disassembled the BIOS and sometimes when I want to know how to access hardware, I read it. But that is hard. Once even I had my own program screwed up, so all the labels (names of line numbers and variables) had changed and made no sense anymore. It was my own program, but stil I hardly understood what it did. bye, shevek 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Egor Voznessenski wrote: I _DO_ have complete, working DOS1 DISKROM source code, I even did huge modifications to it to make it more suitable for HDD Considering the amount of interest in this piece of work, you better up it to funet :-) Eric (wants it too, of course ;-)) 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Hi! Let me join this discussion So, such system software needs to be SOLID: checked, re-checked, checked again, tested, checked again, tested several times more, checked again, tested for a while, re-checked, and this for any important change you make to it. Get the idea? As a part of my long MISIX4 project i made a partial disassembly of DOS2 "kernel" - i use it when i want to know how one or another system call behaves. But i didn't make complete working disassembly - for one plain reason - it is IMHO harder than writing the same thing from scratch. For anyone who wants to join in with such a project, I suggest making a COMPLETE disassembly of DOS1 kernel first: many of the system details used in DOS2 are somehow 'dictated' by what's done for DOS1. I _DO_ have complete, working DOS1 DISKROM source code, I even did huge modifications to it to make it more suitable for HDD interfaceing (eg FAT is not held in memory but is loaded from disk when necessary). I even located and corrected a bug of the original code (it is probably present in ALL diskroms out there, but luckily it needs a very special configuration to show up) Technicaly, adding FAT16 to both DOS1 or DOS2 kernels is not hard. You have to modify 3 routines: - FAT element getting - FAT element putting - add 16 bit FAT processing to them - Cluster Chain processing - must understand both FFx and FFFx special values for respectively FAT12 and FAT 16. Oh yes, and you must of course add FAT16 file system detection routine :-) Greater than 32 Mb partitions are a different story. Modification of kernel for them is not very dificult - you have to modify only multiplication routine in cluster-to-sector translation module. But we don't have any worked-out standards of how to pass this sector number to disk I/O routine! I have an idea about this and I'm testing it now. It seems to work well and is pretty compatible with the "old way". It works as follows: - when sector number is less than 0x, we just work the old way. If sector number is 0x, we forget it and use 32-bit sector number, which is stored somewhere in the BIOS work area. The only thing to be determined and standartized is the location address :-) -- EV [MSX Maniac][Pendorian Wannabe][Tubed Audiophile] [email:[EMAIL PROTECTED]] [www.glasnet.ru/~msxegor] 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/~wiebe/mailinglist/)
Re: IDE driver documentation
On Sat, 7 Nov 1998, Egor Voznessenski wrote: Hi! Let me join this discussion I _DO_ have complete, working DOS1 DISKROM source code, I even did huge modifications to it to make it more suitable for HDD interfaceing (eg FAT is not held in memory but is loaded from disk when necessary). I even located and corrected a bug of the original code (it is probably present in ALL diskroms out there, but luckily it needs a very special configuration to show up) Ooo! You have the DISKROM source code! Could you please send a copy to me through e-mail? With this source code, can I build a faster (ou more optimized) version of the DISKROM? Technicaly, adding FAT16 to both DOS1 or DOS2 kernels is not hard. You have to modify 3 routines: - FAT element getting - FAT element putting - add 16 bit FAT processing to them - Cluster Chain processing - must understand both FFx and FFFx special values for respectively FAT12 and FAT 16. Oh yes, and you must of course add FAT16 file system detection routine :-) That's what I had thought! Greater than 32 Mb partitions are a different story. Modification of kernel for them is not very dificult - you have to modify only multiplication routine in cluster-to-sector translation module. But we don't have any worked-out standards of how to pass this sector number to disk I/O routine! Yes, I think that for 32Mb partitions, the cluster size is equal to the sector size. So, these calculations routines should be completely rewritten. I have an idea about this and I'm testing it now. It seems to work well and is pretty compatible with the "old way". It works as follows: - when sector number is less than 0x, we just work the old way. If sector number is 0x, we forget it and use 32-bit sector number, which is stored somewhere in the BIOS work area. The only thing to be determined and standartized is the location address :-) Perhaps you should work only with 32 bits calculations, because the test for number lower thant h turns the calculation speed variable, which is not desired. Well, this is a detail, but the DISKROM size is limited! Greetings from Brazil! -- Marco Antonio Simon Dal Poz http://www.lsi.usp.br/~mdalpoz [EMAIL PROTECTED] "The measure of success is the knowledge" /"\ \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL / \ 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/~wiebe/mailinglist/)
Re: IDE driver documentation
On Wed, 4 Nov 1998, Jon De Schrijder wrote: No, he's talking about 32MB partitions on IDE-harddisks. I've mailed him a couple of times; but as far as I've understand his work will lead to a dead end: he is working on lowlevel sector read/write routines for IDE, Then you didn't understand it or I didn't make me understand. I'm working on a full driver, and if you want to be able to read files, you'll need to read sectors, right? I told you I'm just beginning my work. but these are already implemented in the IDE-bios of the interface of course. Ok, you work hand-to-hand with Sunrise people and maybe you already have that info. But that's not my case. I mailed Henrik lots of times asking for info on the IDE interface, but I got silence as a response. Finally, I got the source code for Henrik's FDISK and had to start working upon it, and it was my only source of information on the internals of the interface. Maybe you'd like to share with us all the info you have on the interface, because there are still a lot of unknown procedures on fdisk's source code... He hasn't really thought of the fact what should be done next after you can read/write sectors. You can bet I know what to do now that the sector part is finished and that I thinked a lot about that before starting writing anyting. In my opinion -if you want to work with files- you'll have to modify DOS2 kernel routines (sectornumbers#). But he doesn't want to use DOS2. So don't expect real partitions 32MB :-( You're thinking in MSX-DOS(2) terms. I don't. Let's start the 32MB partition discussion again! Ok, maybe we'll get some info this time... 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/~wiebe/mailinglist/)
Re: IDE driver documentation
At 12:14 PM 10/23/98 +0200, you wrote: Hi all! Some of you already knew that I'm writing a new IDE driver that would make possible accessing 32Mb partitions on MSX-DOS(2) via an external shell (maybe a Norton Commander-like) or maybe patching BDOS entry point. Buahhh (Crying) I wanna this driver 4 SCSI! 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/~wiebe/mailinglist/)
Re: IDE driver documentation
Mauricio Braga wrote: Alex Mitsio Sato escreveu: Ooo! You have the DISKROM source code! Could you please send a copy to me through e-mail? With this source code, can I build a faster (ou more optimized) version of the DISKROM? Hi! Could you send me a copy of this source code? I want it too. I want the source code of all about MSX ROMs like BIOS, BASIC, DISKROM, etc. If anybody have it, please, send to my email. Send it to my e-mail too, i would like to study it. thanks. []s Mauricio Braga. Don't you guys have a disassembler? bye, shevek 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/~wiebe/mailinglist/)
Re: IDE driver documentation
There is a Z80 disassembler called Z80DIS which has some sort of "Artificial
intelligence". It ('till now succesfully) detects all kinds of areas like
Instructions, Byte data, Word data, Text data etcetera. But it has some
disadvantages. 1: It can only disassembleup to about 14k of code. After that
the memory is full and it'll break to Dos. 2: it doesn't support "illegal"
(read: unndocumented) z80-instructions.
But ummm... If someone has the Dos2 ROM (RAM) disassembled (in a format so
that I can immediately assemble it again with gen80 without modifications)
could you please send it to me??? I ofcourse prefer a disassembled source
with Ins/Byte/Word/Text-areas...
~Grauw
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/~wiebe/mailinglist/)
