WDCv1.1 final
ZXNet echo conference «zxnet.soft»
Hello budder
There is not enough advanced graphics (I have a Pentagon 1024sl) and then you can do
standard panels like Norton, the convenience of such implementation will increase
several times.
Hello, All
Now the final version of Wild Copier is being prepared for release, so I would like
find out what else is missing in this program, what glitches are encountered (in addition to
documented)?
Among the differences from WDCv1.06 so far there are:
1. Ability to enter TRD images in the left panel
2. Search text on hdd/cd
Hello Vitron
Vit> There is not enough advanced graphics (I have a Pentagon 1024sl) and then you can
Vit> make standard panels like Norton, this is more convenient
Vit> implementation will increase several times.
;)
for WDC such changes will be too drastic, because prog sharpened clearly
for standard Spectrum memory allocation.
It's easier to write a new program using procedures and modules from WDC. There is a project
WC (Wild Commander), which is planned to be more flexible. But yong is still in
initial stage of development (read: only on paper).
Hello budder
So, after all, he will be!!!
This makes me very happy!
Hello Vitron
Vit> So, after all, he will be!!!
Vit> This is very pleasing!
I would like to have more programs for advanced graphics mode.
Including the commander.
Hello, CHRV
CHR> What computers (equipment) does it support.
CHR> Is it possible to write your own driver (for example, for memory management or
CHR> work with IDE)?
Scorpion/KAY 100% compatible + IDE NEMO (separate version for SMUC controller
will be ready this week). There is also WPv0.100 (Wild Player) which has that
same IDE engine as WDC, only the HDD recording functions are removed in it (as well as
working with multi-session CDs). It also supports TS and GS 512.
There is no memory driver option because... no functions that use more than 1
villages.
Regarding IDE controllers, work can be done through the driver (in the source code
The IDE engine is separated into a separate file), but somehow I don’t want to bloat the kernel (there
about 30 procedures called from other modules). It is possible, of course, others
ways to implement. Need to think... ;)
Hello, p@lex
ple> I would like to have more programs for the extended graphics mode.
ple> Including the commander.
WC will be available, the first versions will appear this year. Initially there will be versions
only for the Spectrum screen, but the structure has already been thought out so that one can
work both from the console and in any other graph mode after minor
changes in the source.
But the question immediately arises: how should it differ from WDC in relation to
appearance? What inconveniences do I encounter while working? What features are missing?
Etc. etc. (Ideally, write it down point by point ;) )
Hello budder
It will be more convenient to use if it is similar in appearance and functionality to Honey
Commander 4.01, both for regular graphics and for extended ones.
The ideal commander as I see it for myself on spec is a clone of dos navigator 1.51
it contained everything needed for its time.
Plugins need to be made for ease of use, for example, you copy a file or disk to
hard drive, and there is an error. You'll have to download the disk doctor, but with the plugin....here
he himself suggests trying to restore the file, track, disk :) what
called a micro operating system with artificial intelligence :)
advanced graphics are either tested for presence or two versions of the program.
Since the program is created for normal and convenient operation
hard drive, you can connect a plugin for copying on the spec itself to the screw
protected disks so that it can be autoloaded from a hard drive with
equipment definition.
Hello budder
bud> Now the final version of Wild Copier is being prepared for release, so
bud> I would like to know what else is missing in this program, what glitches
Are bud> found (in addition to those documented)?
bud> Among the differences from WDCv1.06 so far there are:
bud> 1. Ability to enter TRD images in the left panel
bud> 2. Search for text on hdd/cd
What computers (equipment) does it support?
Is it possible to write your own driver (for example, for memory management or working with
IDE)?
Hello, CHRV
CHR> As they say, “not mono but nuno” :-).
CHR> I can also name three controllers that are not supported in particular
CHR> Turbo2+.
;)
There are too many of them. And in our city there are only NEMO IDE controllers. ;)
That's why others are not supported.
Hello budder
bud> Regarding IDE controllers, work through the driver can be done (in
bud> in the IDE source code the engine is separated into a separate file), but the kernel is inflated
bud> somehow I don’t want to (there are about 30 procedures called from others
bud> modules). It can, of course, be implemented in other ways. It is necessary
bud> think... ;)
As they say, “not mono but nuno” :-).
I can still name three controllers that are not supported in particular Turbo2+.
Hello budder
bud> Now the final version of Wild Copier is being prepared for release, so
bud> I would like to know what else is missing in this program, what glitches
Are bud> found (in addition to those documented)?
bud> Among the differences from WDCv1.06 so far there are:
bud> 1. Ability to enter TRD images in the left panel
bud> 2. Search for text on hdd/cd
I would really like there to be a version for flashing into ROM instead of basic-128, with
the ability to record to HDD and work with TR-DOS via 3d13. Then you can
carry out work on a computer with HDD (via WDC) and RAM disk (using Gluk
reset service) without using externally loaded programs at all. Very
convenient and productive, the comfort and speed of working on a computer will increase by
order.
Hello KingOfEvil
Kin> I would really like there to be a version for flashing in ROM instead
Kin> basic-128, with the ability to record to HDD and work with TR-DOS via 3d13.
Kin> Then you can work on a computer with HDD (via WDC) and
Kin> ramdisk (using Gluk reset service) without using it at all
Kin> programs loaded from outside. Very convenient and productive, comfort and
Kin> the speed of your computer will increase by an order of magnitude.
Yes it will be. ;)
But the programmer has not yet been assembled.
Hello Vitron
Vit> Yes, that would be very good, I wouldn’t have to write the commanders again
Vit>
Vit> but I would also like to use , which are accessed as standard
Vit> ports. :) having a ramdisk, they would automatically throw it into the image on
Vit> hard drive.
There will also be a version for #3D13, but you need to launch BASIC under that
do.
Hello KingOfEvil
KingOfEvil wrote:
> I would really like there to be a version for flashing in ROM instead
> basic-128, with the ability to record to HDD and work with TR-DOS via 3d13.
> Then you can work on a computer with HDD (via WDC) and
> ramdisk (using Gluk reset service) without using it at all
> programs loaded from outside. Very convenient and productive, comfort and
> the speed of your computer will increase by an order of magnitude.
Yes, that would be very good, we wouldn’t have to write the commanders again,
but I would also like to use , which access ports as standard. :)
Having a ramdisk would automatically throw it into the image on the hard drive.
Hello budder
bud> ;)
bud> There are too many of them. Yes, and in our city there are only IDE controllers
bud> NEMO. ;) That's why others are not supported.
So this is the whole point of the driver, that you support any controller - even
one that doesn't exist yet :).
If you don’t have time to create a driver structure, give the source code to Max Timonin
(Maxagor), he will debug/add support for the ATM controller for you...
Hello, CHRV
CHR> For this purpose, the source code of the existing implementation is usually provided
CHR> driver (or module) with detailed comments.
CHR> And what do guarantees have to do with it, you give the opportunity, but they can do it
CHR> fans of PRO, Turbo 2+, ZXNEXT, DivIDE... and Kamilevsky
CHR> controller with flash card.
CHR> Otherwise, we should call WDC IDENemo final edition. :v2_wink2;
CHR>;
CHR> And so it turns out, apart from IzDOS, there is not a single cross-clone software.
WDC IDENemoSMUC final edition ;)
(I collected the SMUC version yesterday)
And the guarantee is that creating a driver system will take a lot of time. Yes and
The size after this will not decrease in the program.
(there are comments in the IDE engine, I uncommented them when I was recording to the HDD :) )
Hello budder
bud> If the possibility of additional loading of an external driver appears, then which ones
bud> guarantees that there will be people who will write drivers for that
bud> or other hardware? It's not that simple there.
For this purpose, the source code of the existing driver implementation is usually provided (or
module) with detailed comments.
And what does the guarantee have to do with it, you give the opportunity, and the PRO fans can do it,
Turbo 2+, ZXNEXT, DivIDE... and the Kamilevsky controller with a flash card.
Otherwise, we should call WDC IDENemo final edition. :v2_wink2;
A; then it turns out that apart from IzDOS, there is not a single cross-clone software.
Hello budder
bud> WDC IDNemoSMUC final edition ;)
bud> (SMUC compiled the version yesterday)
bud>
bud> And the guarantee that creating a driver system will require quite a bit
bud> time. And the size of the program will not decrease after this.
bud> (there are comments in the IDE engine, uncommented when recording to HDD
bud> did :) )
I still don’t understand about guarantees.
A guarantee is a kind of obligation... What kind of obligation are you talking about?
Well, as you wish. I just expressed my opinion.
Secondly, the presence of a driver does not mean at all that it should be ADDED to
prog, the driver can replace the base one when configured for a specific clone. Prog
it may even decrease in size if someone writes a driver that is more optimal than
you.
Hello, CHRV
CHR> I still don’t understand about guarantees.
CHR> A guarantee is a kind of obligation... And what kind of obligation are you
CHR> you say?
CHR>
CHR> Well, as you wish. I just expressed my opinion.
CHR>
CHR> Secondly, the presence of a driver does not mean at all that it should be
CHR> ADDED to the program, the driver can replace the base one when setting up
CHR> to a specific clone. The program may even decrease in size if
CHR> someone will write a better driver than you.
By guarantee I meant that the changes will not be in vain, i.e.
someone will find these useful. (The degree of need for such is high or
no?).
I haven’t thought about how to implement the system yet. But most likely (if I do it)
you need to be guided by the fact that there will be a firmware version. Those. one of
drivers must be located together with the body of the program itself.
Hello, CHRV
CHR> So this is the whole point of the driver that you support any
CHR> controller - even one that does not exist yet :).
CHR>
If the possibility of additional loading of an external driver appears, what are the guarantees that
there will be people who will write drivers for that
or other hardware? It's not that simple there.
Hello budder
bud> By guarantee I meant that the changes will not be in vain
bud> i.e. someone will find these useful. (The degree of need for such
bud> high or not?).
Strange question, of course they will come in handy.
Well, for example, we would support ATM turbo right away. The trick is that you are like
the writer supports clones that you do not have and may not have.
bud> I haven’t thought about how to implement the system yet. But most likely (if
bud> I will do it) we need to focus on the fact that there will be firmware
bud> version. Those. one of the drivers must be located with the body itself
bud> programs.
Well yes, that is. in the form of a certain module. It’s worth sorting out the hardware-dependent
parts and independent. The hardware-dependent part is well documented and
install in a specific firmware address space. Well, you are the author for you
more clearly: v2_wink2; .;
Again, this is not a requirement but a wish. This principle of writing software is very
simplifies adaptation - because it does not require the participation of the author and
illumination of sources.
Hello, CHRV
CHR> Well, yes, that is. in the form of a certain module. It's worth dividing
CHR> hardware-dependent and independent parts. Hardware-dependent part
CHR> well documented and set to a specific address
CHR> firmware space. Well, you are the author, you know better: v2_wink2; .;
CHR>
CHR> Again, this is not a requirement, but a wish. This is the writing principle
CHR> software greatly simplifies adaptation - because it does not require it
CHR> participation of the author and exposure of sources.
Yesterday I looked at the source. ;)
There were about 40 hardware-dependent procedures in the IDE engine. quite possible
implement the work through the kernal. (spending an extra 150 bytes somewhere)
True, there are still problems with the firmware version, because... prog no longer fits into 16k.
;(
You will either have to throw out the STC player, or remove any functions
external modules, or optimize everything hard.
Hello, CHRV
CHR> In addition to kernal, there are other methods, for example, like the favorite TRDOS, through
CHR> one point with different parameters. Maybe it will be better this way - for you
CHR> as they say, you know best.
To work through one point, you will have to change almost the entire source code (about 220
source sectors in Storm Assembler format).
And it will take up more memory.
It’s easier with kernal, because the system of external modules has already been partially implemented
(the FDI disclosure procedure, for example, must be downloaded separately).
I'll probably try to do it on Friday. ;)
Hello budder
bud> Yesterday I looked at the source. ;)
bud> There were about 40 hardware-dependent procedures in the IDE engine. That is
bud> it is quite possible to implement such a work through the kernal. (extra 150
bud> bytes spent somewhere)
In addition to kernal, there are other methods, for example, like the favorite TRDOS, through one point with
different parameters. Maybe it will be more optimal - as they say, you know better.
Hello budder
bud> To work through one point, you will have to change almost the entire source
bud> (about 220 sectors of the source in Storm Assembler format).
bud> And it will take up more memory.
bud>
bud> It’s easier with kernal, because the system of external modules has already been implemented
bud> partially (the FDI disclosure procedure, for example, needs to be loaded
bud> separately).
bud>
bud> I'll probably try to do it on Friday. ;)
We are waiting and waiting!
Hello, CHRV
CHR> Waiting, waiting!
Yesterday I made a version for working with the driver. ;)
The only thing I forgot to do was initialize it (so that there are shadow ports
open, etc.)
I also attach an example of an IDE engine for ATM (not working) and for SMUC (it seems
worker). Both sources were made under WDCv1.06, so they are slightly different from
example under IDE NEMO.
P.S. WDCv1.07 itself works with floppy disks, via #3D2F. Under #3D13 version later
I'll do it.
p.p.s. I practically haven’t tested WDCv1.07, so it’s better to use one for now
do not use! :)
File: wdc1_07.zip http://zx.pk.ru/attachment.php?attachmentid=4673
File: examplz.zip http://zx.pk.ru/attachment.php?attachmentid=4674
Hello budder
bud> P.S. WDCv1.07 itself works with floppy disks, via #3D2F. Under #3D13 version
bud> I’ll do it later.
bud>
It's bad that it's 3d2f. Who needs this? It’s inconvenient to constantly switch floppy disks and
wait until it is dr-dr-dr... And a RAM disk is a fast and convenient thing.
Hello KingOfEvil
Kin> It's bad that it's 3d2f. Who needs this? It's inconvenient to have floppy disks all the time
Kin> poke and wait until it is dr-dr-dr... And a RAM disk is a fast thing and
Kin> comfortable.
I need it! ;)
Not all frames have a disk... And disk errors are processed in the main
versions.
There will be a later version under #3D13. :)
Hello budder
bud> I need it! ;)
bud> Not all frames have a disk... And disk errors are processed in the current
bud> main version.
bud> There will be a later version under #3D13. :)
We are waiting...
Hello KingOfEvil
Kin> Waiting...
In about two weeks there will be a version #3D13. :)
Right now I'm busy studying... ;(
Hello budder
Updated the WDC version, download there.
Version 1.072 added the ability to initialize the driver. Also edited
some glitches.