IDE question
ZXNet echo conference «hardware.zx»
Hello Vovoi
Vovoi, all your questions are feasible.
Hello Zet9
Zet> Why not?
Zet> Yes!!!
Zet> If you have Matlash-Avryata TR-DOS firmware in the ROM, you can work with
Zet> TRD images directly from the screw (even on Spectrum-128),
Zet> intercepts reading and writing via #3D13, but TRD images must
Zet> be continuous (which is generally not a problem).....
Software question: The TR-DOS ROM driver sees 640Kb of disk space,
iS-DOS software driver up to 16MB.
How many megs of hard drive can the Z80 processor itself support?
real spec? That is, Speck is not able to read RAM address 65536 and higher,
that's why Sir Sinclair divided the RAM into pages, but what about the
external devices, this is sewn into a Nam (or similar) controller or that’s it
is it easily made from asma? Well, accordingly, let’s say when we receive such
programs, will it be possible to read a gigabyte, say, text file? I understand
That’s a lame question, but how is this whole kitchen organized?
It is very interesting to know the opinion of experts.
Hello Vovoi
Vov> Software question: ROM driver TR-DOS sees 640Kb of disk space
Vov> spaces,
1mb
Vov> How many megas of hard drive can the Z80 processor itself support and
Vov> is it really a real spec?
what kind of driver you write will be the same, at least support ntfs on a 300GB screw
lba 48
Hello Vovoi
Vov> How many megas of hard drive can the Z80 processor itself support and
Vov> is it really a real spec?
The size of the screw is strictly parallel to the processor itself.
> That is, Speck is not able to read RAM address 65536 and higher, because
> Sir Sinclair divided the RAM into pages, but what about
> external devices, this is sewn into NAM (or similar)
> controller or is everything done easily from ASMA?
Nothing is hardwired into NAM's - the controller is just a bunch of
microcircuits with buffers and a decoder for new ports - i.e. some kind of adapter between
IDE connector and Spectrum board signals.
So everything is done from ASMA (in the case of iS-DOS, this is loaded firewood).
> Well, and accordingly, let’s say when you receive such a program, will it be possible
> read a gigabyte, say, text file?
It depends on the program. In iS-DOS, for example, it is possible. However, not gigabyte, since
the size of one partition on a screw is no more than 16MB, and the maximum file size,
determined by the properties of the file system, barely exceeds 5MB. But in the agreed
5MB limits - maybe. If we imagine another file system without these
restrictions (for example - pisish FAT), then gig is possible.> I understand that the question is lame and yet, like this whole kitchen
> being organized?
> It is very interesting to know the opinion of experts.
Only a small part of the text is read (as much as the editor or viewer allows),
az then, when scrolling, they quickly pump up one by one, one after another,
other parts.
Hello demon_zx
dem> In fact, in IS-DOS it is possible to create a file almost 16 in size
dem> MB, but this cannot be done using the system 8-).
Here! This is what I wanted to know.
That is, the authors of iS-DOS could well have cut up partitions larger than 16MB, right?
What was stopping them, some hardware difficulties or lack of RAM for the driver?
:(
The> /TR-DOS sees 640Kb of disk space/
The> 1mb
The>
I want a format file for meg for real, please come to the studio!
:p
* The rest is clear, I was very pleased, thank you. In any case, who in
the system wants to use all the gigabytes of the screw, I’ll leave the window in the RAM for
drivers.
* Regarding the scrolling of the gig text, (Maksagor thnx) this is what I wanted to expect,
I’m glad that this is the case, which means that in theory you can run programs on spec
at least a few megabytes in size (the size of the RAM), an incredible glitch
will be provided.
:)))
Hello, Maksagor
In fact, in IS-DOS it is possible to create a file almost 16 MB in size, but
This cannot be done using the system's means 8-).
Hello, Maksagor
> So, for the numbering of blocks, the authors allocated only two in the file descriptor
> bytes, and not, say, three (although they had such an opportunity). As a result
> we get a maximum of 65536 blocks or 16MB.
Well that's cool! You are great for sculpting TASiS based on iS-DOS, nada
put 4 bytes :)))
Hello Vovoi
Vov> Here! This is what I wanted to know.
Vov> That is, the authors of iS-DOS could well have cut up partitions and more than
Vov> 16MB, right? What stopped them, some hardware difficulties or
Vov> lack of RAM for the driver? :(
No, it was meant that the features of the file system allow you to create a file
the size of the partition itself (up to 16MB). The partition itself cannot exceed this size
maybe. The reason is not hardware limitations, but a lack of the file system itself
iS-DOS, incorporated during its development: the volume of the device is measured in blocks of 256
byte each. So, for the numbering of blocks, the authors in the file descriptor allocated only
two bytes, and not, say, three (although they had such an opportunity). As a result
we get a maximum of 65536 blocks or 16MB. Why did they do this? Fuck it
knows. Apparently, at that time (1992-93) they did not think that hard drives and others like them
They will eventually become part of the life of the Spectrum and larger volumes will be required. In general,
it turned out something similar to the statement of Bill Gates - “640 kilobytes is enough for
everything."
> I want a format file for MEG for real, please come to the studio!
> :р
If you get not an 80-track drive, but at least a 100-track drive.
Because exceeding the volume of 640Kb in a standard TR-DOS floppy disk is onlywhen going beyond 80 lanes (on real flops it turns out to reach
sometimes tracks 83-84).
Hello, Maksagor
> If you get not an 80-track, but at least a 100-track
> disk drive. Because the volume exceeds 640Kb in standard TR-DOS
> a floppy disk is obtained only when it goes beyond 80 tracks (on real
> flops sometimes reach track 83-84).
Indeed, it purely depends on the drive model. I had a disk drive from
computer AGAT-7. Import. 84 tracks. The head block is 4 times more compact than
was in Soviet disk drives. However, with careful modification of the latter, it is possible
to marry their family 80. It’s just that beyond the 80th path my head just rested on
structural details.
Hello Vovoi
Vov> Well that’s cool! Well done for sculpting TASiS based on iS-DOS, right
Vov> need to add 4 bytes :)))
It would be easy to lay it down if we sculpted something of our own. But in fact it is necessary
think about how to painlessly redo what was already laid many years ago. Above this
We’re thinking a little at a theoretical level, but it hasn’t gotten to the point yet...
Hello, Ivan
In order to use the screw completely under isdos (I have 1.2 GB) I wrote
a program that quickly and conveniently switches partitions on the screw, figuratively speaking
The screw is divided into a bunch of 16 M partitions.
Hello, Peter
Hello!
I have several questions regarding the IDE controller and hard drive.
I purchased a Pentagon 1024SL 2.2 board and an IDE controller for it
connecting the IBM Deskstar IC35L040AVVA07-0 40.1GB screw nothing happens, no
auto-detection, heads do not crack, the controller is inserted correctly into the board, on
pc screw works. Should it be visible through the Gluk 6.3 menu?
or is it a problem with decoding such a volume of screw that I will have to look for more
less (though there is 4.3 gigs, but it doesn’t work)...
what happens when you turn on a computer with a screw on such a computer, what
wired programs allow them to be used immediately, do you need to divide the screw like a nibub
(there is boot from disk in the menu)..?