Re: IDE driver documentation

1999-02-10 Thread NYYRIKKI
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

IDE driver documentation

1999-02-10 Thread ag0ny
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. As I'm not a good assembler programmer, I decided to release the full

Re: IDE driver documentation

1999-02-10 Thread Jon De Schrijder
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

Re: IDE driver documentation

1999-02-10 Thread ag0ny
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.

Re: IDE driver documentation

1999-02-10 Thread Javi Lavandeira Montes
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

Re: IDE driver documentation

1999-02-10 Thread Alex Mitsio Sato
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

Re: IDE driver documentation

1999-02-10 Thread Egor Voznessenski
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

Re: IDE driver documentation

1999-02-10 Thread Maurizio
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

Re: IDE driver documentation

1999-02-10 Thread Mauricio Braga
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

Re: IDE driver documentation

1999-02-10 Thread Laurens Holst
: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

Re: IDE driver documentation

1999-02-10 Thread shevek
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.

Re: IDE driver documentation

1999-02-10 Thread Eric . Boon
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

Re: IDE driver documentation

1999-02-10 Thread Egor Voznessenski
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

Re: IDE driver documentation

1999-02-10 Thread Marco Antonio Simon dal Poz
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).

Re: IDE driver documentation

1999-02-10 Thread Javi Lavandeira Montes
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

Re: IDE driver documentation

1999-02-09 Thread Ricardo Jurczyk Pinheiro
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)

Re: IDE driver documentation

1999-02-09 Thread shevek
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

Re: IDE driver documentation

1999-02-09 Thread Laurens Holst
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