From
Alex Freed
→
To
All
17 November 2005
Hello, All
Please don't blame me for asking stupid questions: I don't know Speck very well.
There is a file TEST4-30.$B. Runs great in the emulator. And for me
it needs to be on hardware. There is nothing except the tape port.
I learned how to launch TAP. The question is how to recode?
As I understand it, $B is a “hobet” file. Apparently a basic launcher.
I tried to save it as a TAP in emuzwin but it doesn’t load.
Moreover, the file is smaller than the original $B - suspicious.
From
SMT
→
To
All
17 November 2005
Hello alexfreed
most likely a monoblock. that is, a small BASIC loader + glued
program sectors. to translate into tape, without a little manual work
get by
From
Vlad Semchenko
→
To
All
17 November 2005
Hello alexfreed
If there is a real one, then the file is saved on the MS-DOS disk and launched on spec
TRMSHOB utility (available at trd.speccy.cz), and simply copying is performed
file from MS-DOS disk to TR-DOS. There are other programs, in particular you can file
First, drive it into SCL and pull it out on Spec using the appropriate utility. In extreme
case, you can transfer the file to TR-DOS in any way, and cut off the first ones (it seems
13 bytes), and what remains to be written as file.B.
You can also run it on a PC under MS-DOS (or in DOS emulation mode under Win)
Spectrum Navigator and opening the file from the PC disk (screw) copy it to TR-DOS
floppy disk It may not work under NT (Win2000, WinXP).
From
Vladimir Kladov
→
To
All
17 November 2005
Hello spensor
how did you save it in .TAP? There is File | Save as... select .TAP - through
EmuZWin Loader. This is an analogue of the magic button - for resetting to .TAP format, and not to
disk. If it is then loaded into the emulator, then the size does not matter :) And
then you can try to dump it onto tape to load it into real life.
From
Alex Freed
→
To
All
18 November 2005
Hello, Vladimir Kladov
Vla> Yes File | Save as... select .TAP - via EmuZWin Loader. If he
Vla> is then loaded into the emulator, then the size does not matter :)
That's what I did. Only it didn’t load into the emulator. And apparently size matters: TAR
These are all the bytes of the program plus the header. In theory, the monoblock should be the same
ok...
And who can enlighten me: how are monoblocks made? Everything is clear from the tape:
LOAD "ABCD" CODE ... and then the data. How is the $B file structured?
I don’t mind rebuilding it manually, but you need to know the format of the source file.
From
Alex Freed
→
To
All
18 November 2005
Hello caro
car> Two test conversion options
car> program test4_30.$B in TAP format:
car>
Thank you, Kamil, but unfortunately it seems that not a single method works.
I'm trying to load it into the emulator first. EmuZWin v2.7
If a Pentagon with TRDOS is emulated, then everything is fine. What if it's just
128, then both options hang the computer, but in different ways. Probably either in the test itself
something is tied to TRDOS, or when saving some remain
appeals. If I have time, I'll try to follow it in the emulator.
Since the emulator hangs, it’s not surprising that the hardware does too. It's a pity - I wanted
check your memory expansion.
Maybe someone else knows the tests?
From
SMT
→
To
All
18 November 2005
Hello alexfreed
ale> who can enlighten me: how monoblocks are made
The BASIC loader looks like
1 REM... (codes)
2 run usr 23xxx
in the codes NN sectors are read, starting from the current sector, on which
this BASIC has ended (there is such a TR-DOS variable), after which JP start
After BASIC, a code file is immediately written. and then these 2 files are merged into
one. the "length in sectors" field is the sum of the lengths of 2 files, and the "length in bytes"
remains the same as the first loader file, so that the beginning, the name, is loaded into memory
file - from the first file
so you need to put a break before running the code block and save the block in
separate file
From
Kamil Karimov
→
To
All
18 November 2005
Hello alexfreed
ale> "There is nothing except the tape port." And there is no other real either.
Two test conversion options
program test4_30.$B in TAP format:
1) The file test4_30.tap was obtained by saving
memory areas from addresses 6000h to 9400h
after downloading and running the test in the emulator
Unreal.
It starts like this:
LOAD "" CODE : RANDOMIZE USR 24576
2) The file test430.tap was received on recommendation
Vladimir Kladov loading the test in the emulator
EmuzWin and saving the program in TAP format.
It starts like this:
LOAD ""
File: test430.zip http://zx.pk.ru/attachment.php?attachmentid=1960
From
Alex Freed
→
To
All
18 November 2005
Hello SMT
SMT> the BASIC loader looks like
SMT>
I'm afraid I don't understand.
1 REM... (codes)
2 run usr 23xxx
like the Basic file contains all the codes? Then why are we talking about two glued ones?
failah? Maybe there is a document somewhere? Actually I want to understand how
extract clean codes from .$B file. To load from the tape. I have the disk
not expected yet :(
From
SMT
→
To
All
18 November 2005
Hello alexfreed
> like Basic file contains all the codes
no, just the bootloader code. usually BASIC takes 1-2 sectors
> Maybe the document is somewhere?
too standard and obvious solution, used in almost all
disk programs, why bother documenting them?
> Actually, I want to understand how to extract clean codes from the .$B file
cut off the hobeta header. see the length of the basic. if less than 256 bytes, then
bite off 1 sector from the file from the beginning, less than 512 - 2 sectors, etc. everything
the rest is a code block. look at the download and launch address under the emulator
inside the bootloader
From
Vlad Semchenko
→
To
All
21 November 2005
Hello alexfreed
ale> "There is nothing except the tape port." And there is no other real either.
Sorry for the inattention :(
ale> Probably either in the test itself something is tied to TRDOS, or
ale> saving some remain
ale> appeals.
This is unlikely. As far as I remember, the program is quite smart and straightforward. So that she
to start it was enough to drive the code block into memory and make USR on the first one
download address. There is no critical connection to anything there. On my tape
(if it is still “alive”) this test is located (maybe v4.20, which is in this
not important in case). If anyone can tell me how to move a file from tape to
PC, I'll try to provide it. The fact that she worked on the 48th with tape is a fact.
From
Kamil Karimov
→
To
All
21 November 2005
Hello spensor
spe> As far as I remember, the program is quite smart and straightforward. So that her
spe> to run it was enough to drive the code block into memory and do USR
spe> to the first download address.
All versions of this program (4.18 --- 4.30) have the following entry in the code:
'IMP PROTECTION SYSTEM '95"
It looks like you can't just pull out the code and run it.
From
Alex Freed
→
To
All
10 December 2005
Hello spensor
spe> Sorry, for inattention:(
spe>
spe> This is unlikely. As far as I remember, the program is quite smart and
spe> uncomplicated. To start it, it was enough to enter the code
spe> block into memory and make a USR to the first load address. Critical
spe> there are no strings for anything there. On my tape (if it is still
spe> "live") this test is located (maybe v4.20, which is in this case
spe> not important). If anyone can tell me how to download a file from tape
spe> on PC, then I’ll try to provide it. The fact that she worked on the 48th with tape
spe> this is a fact.
I followed it in the simulator: the program quickly tries to go to the trdos ROM,
but he’s not there. So we need to look for another test. Or write. Or maybe old
version didn't require trdos?
From
goodboy
→
To
All
10 December 2005
Hello alexfreed
managed to remove calls to the trdos ROM from the test
File: TEST.ZIP http://zx.pk.ru/attachment.php?attachmentid=2079