Which emulator?

[Which emulator?]

Version 3.0 of the p-code-tool is ready. I needed this program for myself, but everyone who thinks he can use it, can download it for free.

You can now handle 1440 sector disks (720 blocks in Pascal) with it. Also you can resize a 360 sector, or 720 sector disk to a 1440 sector disk (sector or track image file).

I also made a short manual for it.

p-code-tool-V3.0.exe manual.pdf

[Which emulator?]

until V3.0 is ready, you can use this version V2.2

every imported textfile gets now a '.TEXT' extention.

The program checks if the name already exist and put '01' behinde the name when it does.

This version can only use 360 block disks (TI 720 sectors). When you open a 720 block disk there is no warning. 

Version V3.0 will be able to use 720 blocks.

 

The commands 'Get P-code file' and 'Get Data-file' are not checking if there is already a file with the same name.

When you import those files, I assume you will need the same name.

 

p-code-toolV2.2.exe

[Which emulator?]

The problem is not in the arrangemend of the disk, that i good news  

My program looks for the disksize to the amount of sectors in block 0. For the disk made by Fred Kaal it says 720 sectors, even when it are 1440 sectors.

In the 'Save as' commando, i count the real amount of sectors.

The 'Crunch' command does not go beyond the disksize, so the sectors above 720 do not move, but the addresses to those files in the FDR have changed.

When i use the real amount in the 'Crunch' command, everything was working again.  

I will make a new version of this program (V3.0) and i will change the disksize for new P-code disks to 1440 sectors or 720 blocks. 

[Which emulator?]

first explanation, i will work this out furder:

 

when you open the PHOENIX disk with my tool, you see that there are 720 TI-sectors and 720 P-code blocks on your disk.

my program is working for 720 TI-sectors and 360 P-code blocks

Your disk is singel density and double sited. you can see this with 'View block' in block 0 after the TI-disk name 02D0 = 720 sectors.

Also with 'View block' you can see in block 2 after the P-code disk name there is 02D0 or 720 blocks on the disk.

TI has sectors of 256 byte, P-code uses blocks of 512 byte.

When I press 'Save as' i see that the program counted 1440 sectors.

So somehow the diskinfo is not right.

How did you make this virtual disk ?

 

What went wrong:

When you open your PHOENIX disk and you click on Extented Disk info left under, you will see an empty space of 318 sectors between file 9 and 10.

When a text file is changed with Notepad, the program deletes the old file, crunch the disk and writes the changed file at the end. 

 

I have to see how the sectors are arranged in this kind of disk. I use the normal TI layout:

first side the sectors 0 to 359 = sector 0 at the start, sector 359 at the end

second side the sectors 719 to 360 = sector 719 at the start, sector 360 at the end 

This way when you have to write sector 360 after 359 the writing head does not have to go back to the beginning 

 

When the second side on your (virtual) disk begins with 360 then it will explain the error. I'll study your disc more closely.

With the tools 'View Block' , 'Extend Disk info' and 'showing contend of' you can examen the disk.

The disk image that you have opened with my program does not change until you press ReSave or when you Overwrite it with 'Save Disk'.

 

[Which emulator?]

i will take a look at it !

[Which emulator?]

Relieved

With the testing i also forgot sometimes to click on ReSave.

When you still have a file, that you can not import as text, let me know and if possible send me this file. 

Perhaps i have to make the import buffer longer, when you have an error with a big file.

 

I will make a version 2.2 where the extention .TEXT will be added right away, when you  import a text-file.

In this new version the text in the block 'Save as' will be on the right place too.

 

The import text command accepts only the ascii characters 32 to 126, the tab (ascii 9) and the return (ascii 13), all other characters are lost.

Let me know if you would like to include those lost charaters in a way like [127] for character 127. (for a programfile this would not help of course.)

Also the length of a line is 77 characters all other characters are lost too. The text-file must be end with a return (ascii 13 and ascii 10) when there is none at the end of the file, the import command will add a ascii 10. 

I noticed at some point during the testing that i got a character 11 at the end of the file, but i could not reproduce it. Version 2.2 will check for a character 11 at the end and remove it.

 

[Which emulator?]

I does not matter if the .TEXT is appended in the tool or intern.

 

[Which emulator?]

1 hour ago, apersson850 said:

It's probably the creation of the special header p-system text files have that fails. The first two blocks (1 Kbyte) are used to store the things you can see if you use Set Environment in the Editor. When you create a new file, the simplest solution would probably be to just retrieve a copy of this data from a new text file, created by the p-system itself, and just change the minimum required (like the creation date). Maybe there's a size in there too - don't remember.

I made indeed a copy of the first two blocks and only changed the date  

There is no size in these blocks, the last block must be filled up with zeros.

 

Can you test something for me Apersson850?

Can  you import a tekstfile that you could not read in P-code and then with 'CHANGE NAME' append the filename with '.TEXT' (press ReSave) and try to read this file now?

I noticed when i was testing that i can not get a textfile with the Filer G(et command when the filename did not end with '.TEXT' 

(you must not type the '.TEXT' in the Filer G(et command ) 

 

[Which emulator?]

I use this pcode tool indeed as an Editor/filer.

Of course i can make this tool to support every disk image size you want, but when i was testing a  1440 sector disk, P-code made a big mess of it. That's why I went back to a 720 sector disk (360 sectors in P-code). I assumed this is the maximum that P-code can handle.

Let me test it again with other TI-emulators ( and perhaps without using the Editor/Filer programs.  )

I am using the CADD emulator. 

[Which emulator?]

I am indeed the creator of this tool.

I use it to make Pascal and Assembler programs in P-code.

With this tool I also have a quick way to see the contents of a disk (and the files) and to move the files (by save them first to windows) to an other disk.

I noticed now the error in the text files transferd from windows to the disk and i will fix it in version V2.2

On 8/13/2020 at 8:32 PM, Vorticon said:

One point: there seems to be an issue with accessing the right mouse button menu for the files on disk. Sometimes it works and sometimes not.

I was not able to reproduce the right click error in the file-popup, but i notice that the last popup was still visible when i click om 'empty', i will fix this too.

When there are other problems with this popup or with this program, let me please know.

 

With version V2.1 you can edit a disk that is in use by the emulator, this was not possible in version V1.0. So you can ignore what is told about the need to swap the disks.

With ReLoad and ReSave you can reload or resave the disk that is opened with 'Open Disk', it is a quick way to save and load, but I think, that I do not need to tell, that you have to use it with canniness ... 🙂 When you click on ReLoad in stead of ReSave your changes are gone. Use ReLoad when you made changes on the disk in the emulator, that you want to see in the tool. Use ReSave when you want to save the changes, you made on the disk in the tool, to the disk-file. I did no see the benefit of building in a "are you sure" popup .... 

With 'Open Disk' you can open also some P-code disks that do not have the TI FDR, so you can read P-code disks from some other computers.

The way i used this tool at the moment:

1. Open disk1 with 'Open Disk'

2. Open SYSTEM.WRK.TEXT at the disk in notepad with right-click

3. Make changes in the programfile

4. Save and close notepad

5. Click ReSave

6. Compile the program 

7. When there are some errors I right-click on SYSTEM.WRK.TEXT and make the canges in notepad (at this moment there is no need for ReLoad)

I repeat 5 till 7 until the program is ready

 

 

[A my mode for say big thanks at all TI99 Community.]

Thank You Ermanno, for all this work !!

[New TI-99/4A Tunnels of Doom(TOD) game and Game Editor]

i want to give it a try too !!!

TOD was next to Adventure my favorite game