Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store
IGNORED

TIPI Usage and Support

jedimatt42

By jedimatt42
in TI-99/4A Computers

 Share

Recommended Posts

jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

Myarc Mode does not "lock in", it always returns to TI mode, I figure there must be a reason for this, but I also think the time has come for a new TIPI support program.

 

Now many of us know PALEA5 for the F18A, you run it and that's it, settings changed and it quits. I'd like to see a small EA/5 program for the TIPI that does this as well. You run it, and it changes TIPI to "Myarc Mode" and quits, that's it. We could run it when we need it, and it would be super easy from BOOT/9640 Menu System or as a call in a BATCH file in 4A/DOS.

 

Well, first, I'd like to pursue not needing Myarc mode.

 

That should be simple for someone to write though :

step 1: find the crubase for the user's TIPI ( there is source for this in the TI Artist driver )

step 2: set crubit 3 of the tipi on. ( there is source for this in the TIPICFG application )

step 3: BLWP @>0000 or a kinder return if 4ADOS supports it.

 

-M@

Shift838 River Patroller

Shift838

Posted
Posted (edited)

I have verified after the update I can save to a physical floppy.

 

However, I still cannot copy from the TiPi to a physical floppy. Getting closer though. It actually tries and i can see it access DSK1 but then DM2k responds with error 0: Opensrc [Device Name]

Edited by Shift838
  • Like 1
jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

Myarc mode doesn't lock in, because you are only meant to use it as a temporary work around when performing disk management, until "TIPI." is supported by a disk manager tool. I have started authoring TIPIMAN. But that will take time.

 

Myarc mode should persist across hard resets even power events on the console, as long as the tipi-board is still powered up... I'll play with that some-more and see if it is behaving correctly... it appeared correct in my testing last night.

 

The other reason I didn't persist this, is my only persistence is on the PI. And I'm avoiding interaction with that one console powerup routine as possible so TIPI doesn't slow down console resets. Console reset is as far as I can tell THE most used feature on the 4A. Everyone would grown if I made it slow.

 

-M@

jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

I have verified after the update I can save to a physical floppy.

 

However, I still cannot copy from the TiPi to a physical floppy. Getting closer though. It actually tries and i can see it access DSK1 but then DM2k responds with error 0: Opensrc [Device Name]

 

Yes, to copy from a tipi hosted storage to real DSKx devices, you have to go into TIPICFG, switch to Myarc mode and then copy from tipi as WDS1. to your real floppies. Level 2 IO, in this case, seems to be accessed by a DSRLNK that doesn't support the cascade feature that the console rom uses.

 

Then after you are done copying you should be able to switch back to TI FDC mode for the tipi in TIPICFG. For most programs, you should still be able to access your real DSK devices if tipi simply doesn't have them mapped. However given the nature of legacy software, you may still have to switch to Myarc mode to disable the tipi's DSK prefixed device names altogether.

 

I'd like to know about software in active use that actually requires that.

 

-M@

Shift838 River Patroller

Shift838

Posted
Posted

 

Yes, to copy from a tipi hosted storage to real DSKx devices, you have to go into TIPICFG, switch to Myarc mode and then copy from tipi as WDS1. to your real floppies. Level 2 IO, in this case, seems to be accessed by a DSRLNK that doesn't support the cascade feature that the console rom uses.

 

Then after you are done copying you should be able to switch back to TI FDC mode for the tipi in TIPICFG. For most programs, you should still be able to access your real DSK devices if tipi simply doesn't have them mapped. However given the nature of legacy software, you may still have to switch to Myarc mode to disable the tipi's DSK prefixed device names altogether.

 

I'd like to know about software in active use that actually requires that.

 

-M@

 

confirmed, the Myarc mode works. I can copy from TiPi to real floppies.

  • Like 1
jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

The TipiPEB board wiring to the PI is not explicitly called out anywhere... Beery pointed out...

 

The wiring is documented here: https://github.com/jedimatt42/tipi/wiki/TIPI-to-PI-Wiring

 

The hook up is the same as for the sideport TIPI.

 

I'll try and improve this from spec' to diagram tonight.

 

-M@

9640News River Patroller

+9640News

Posted
Posted

https://github.com/jedimatt42/tipi/wiki/TIPI-to-PI-Wiring#connecting-the-cables

 

I hope this picture is clear, if it is not, I would welcome the feedback.

 

-M@

 

Matt,

 

Yes, that picture is clear. At work now, so will look things over tonight or tomorrow as time permits. Probably would not hurt to add that information to the webpage URL that is on the card.

 

Beery

Omega-TI Quadrunner

Omega-TI

Posted
Posted

Here is the last part of the log, when I attempted to move a PROGRAM called REMIND from "WDS1.DOS." to "DSK1."

 

The file size of REMIND is 33, but ends up transferring as a DIS/FIX 0 file with a length of 1.

 

I started off with an entirely new .HFE file called HXC instead of TIPI....just in case, as you expected, no difference.

 

 

2018-08-17 18:32:11,265 LevelTwo : INFO unit: 1, path: WDS1.DOS.
2018-08-17 18:32:11,266 tipi.TipiMessage: INFO waiting to send message...
2018-08-17 18:32:11,266 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,268 tipi.TipiMessage: INFO sent msg len 1, rate 619 bytes/sec
2018-08-17 18:32:11,269 TipiService : INFO waiting for request...
2018-08-17 18:32:11,269 tipi.TipiMessage: INFO waiting to receive message...
2018-08-17 18:32:11,270 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,271 tipi.TipiMessage: INFO received msg len 1, rate 1506 bytes/sec
2018-08-17 18:32:11,272 LevelTwo : INFO direct input
2018-08-17 18:32:11,273 tipi.TipiMessage: INFO waiting to receive message...
2018-08-17 18:32:11,273 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,275 tipi.TipiMessage: INFO received msg len 2, rate 2277 bytes/sec
2018-08-17 18:32:11,276 tipi.TipiMessage: INFO waiting to receive message...
2018-08-17 18:32:11,276 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,280 tipi.TipiMessage: INFO received msg len 10, rate 3689 bytes/sec
2018-08-17 18:32:11,280 tipi.TipiMessage: INFO waiting to receive message...
2018-08-17 18:32:11,281 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,283 tipi.TipiMessage: INFO received msg len 2, rate 2269 bytes/sec
2018-08-17 18:32:11,283 LevelTwo : INFO unit: 1, blocks: 0, filename: REMIND, startblock 0
2018-08-17 18:32:11,284 tipi.TipiMessage: INFO waiting to send message...
2018-08-17 18:32:11,285 tipi.TipiMessage: INFO waiting for handshake...
2018-08-17 18:32:11,286 tipi.TipiMessage: INFO sent msg len 1, rate 658 bytes/sec
2018-08-17 18:32:11,287 TipiService : INFO waiting for request...
2018-08-17 18:32:11,288 tipi.TipiMessage: INFO waiting to receive message...
2018-08-17 18:32:11,288 tipi.TipiMessage: INFO waiting for handshake...

arcadeshopper Quadrunner

+arcadeshopper

Posted
Posted

 

I came up with a nicer solution:

 

post-25598-0-90126500-1534542407_thumb.jpg

  • Like 3
9640News River Patroller

+9640News

Posted
Posted

OK,

 

I plugged my TIPI-Peb into the PEBox that contained the interface card, RS232, Myarc HFDC (CRU >1100) and a Myarc 512K card.

 

When I turned the system on, the TI would not boot. My first thought there was a CRU conflict so I adjusted the CRU on the TIPI. System booted, and I went to the TI Basic prompt.

 

I typed "CALL TIPI" and got no response. I think it was an error message.

 

Thinking there was an issue with the Myarc HFDC and conflicts I started to change the CRU on the Myarc HFDC and move the TIPI back to the default, then it dawned on me the Myarc 512K card was potentially the conflict.

I pulled the Myarc 512K card and replaced with a TI 32K card. I went back into TI Basic and typed in "CALL TIPI".

 

The system started to load, then the screen went yellow. Waited a couple of minutes, nothing, still a yellow screen.

 

Ideas?

 

Beery

 

jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

OK,

 

I plugged my TIPI-Peb into the PEBox that contained the interface card, RS232, Myarc HFDC (CRU >1100) and a Myarc 512K card.

 

When I turned the system on, the TI would not boot. My first thought there was a CRU conflict so I adjusted the CRU on the TIPI. System booted, and I went to the TI Basic prompt.

 

I typed "CALL TIPI" and got no response. I think it was an error message.

 

Thinking there was an issue with the Myarc HFDC and conflicts I started to change the CRU on the Myarc HFDC and move the TIPI back to the default, then it dawned on me the Myarc 512K card was potentially the conflict.

I pulled the Myarc 512K card and replaced with a TI 32K card. I went back into TI Basic and typed in "CALL TIPI".

 

The system started to load, then the screen went yellow. Waited a couple of minutes, nothing, still a yellow screen.

 

Ideas?

 

Beery

 

 

If you got an error message in the first round from BASIC, then there was probably a ROM conflict... 'Bad Name' should have been the error. This was with an adjusted CRU? It shouldn't have happened. What was the cru adjusted to?

 

I'll see if I can find info on the hardware I don't have... Do you have the manual for your Myarc 512K? I believe those had DSRs for and ram in the DSR space... but I have never seen the manual.. I would assume it would also detail what crubase the card uses. You should root cause that failure.

 

Does the 32k you put back in pass the memory test? https://github.com/jedimatt42/ti994a-32kmemtest/releases/download/v1.3/32kexptest.bin

 

CALL TIPI is an EA5 loader. with no arguments, it loads "TIPI.TIPICFG" into expansion ram..

 

It sounds like it loaded it, but is corrupted in ram, or in transit... so eliminate the question of ram by running that ram test. For the test to work, the pathways through the flex cable, console, and 32k have to be good.

 

CALL TIPI should load and run in less than 5 seconds.

 

Don't discount dirt and goo in peb slots that have been unused for decades...

 

-M@

  • Like 1
jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

Here is the last part of the log, when I attempted to move a PROGRAM called REMIND from "WDS1.DOS." to "DSK1."

 

The file size of REMIND is 33, but ends up transferring as a DIS/FIX 0 file with a length of 1.

 

I started off with an entirely new .HFE file called HXC instead of TIPI....just in case, as you expected, no difference.

 

 

2018-08-17 18:32:11,265 LevelTwo : INFO unit: 1, path: WDS1.DOS.

2018-08-17 18:32:11,266 tipi.TipiMessage: INFO waiting to send message...

2018-08-17 18:32:11,266 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,268 tipi.TipiMessage: INFO sent msg len 1, rate 619 bytes/sec

2018-08-17 18:32:11,269 TipiService : INFO waiting for request...

2018-08-17 18:32:11,269 tipi.TipiMessage: INFO waiting to receive message...

2018-08-17 18:32:11,270 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,271 tipi.TipiMessage: INFO received msg len 1, rate 1506 bytes/sec

2018-08-17 18:32:11,272 LevelTwo : INFO direct input

2018-08-17 18:32:11,273 tipi.TipiMessage: INFO waiting to receive message...

2018-08-17 18:32:11,273 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,275 tipi.TipiMessage: INFO received msg len 2, rate 2277 bytes/sec

2018-08-17 18:32:11,276 tipi.TipiMessage: INFO waiting to receive message...

2018-08-17 18:32:11,276 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,280 tipi.TipiMessage: INFO received msg len 10, rate 3689 bytes/sec

2018-08-17 18:32:11,280 tipi.TipiMessage: INFO waiting to receive message...

2018-08-17 18:32:11,281 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,283 tipi.TipiMessage: INFO received msg len 2, rate 2269 bytes/sec

2018-08-17 18:32:11,283 LevelTwo : INFO unit: 1, blocks: 0, filename: REMIND, startblock 0

2018-08-17 18:32:11,284 tipi.TipiMessage: INFO waiting to send message...

2018-08-17 18:32:11,285 tipi.TipiMessage: INFO waiting for handshake...

2018-08-17 18:32:11,286 tipi.TipiMessage: INFO sent msg len 1, rate 658 bytes/sec

2018-08-17 18:32:11,287 TipiService : INFO waiting for request...

2018-08-17 18:32:11,288 tipi.TipiMessage: INFO waiting to receive message...

2018-08-17 18:32:11,288 tipi.TipiMessage: INFO waiting for handshake...

 

 

Thanks, that isn't healthy... you would expect to see multiple "direct input" requests.

 

I've narrowed it down to "AINT" GONNA WORK" without a TIPI aware disk manager. Level 3 IO to devices after the TIPI work fine, read and write...etc... but Level 2 IO used by disk managers doesn't cascade. And in this case, when we are pretending to be WDS1., my Level 2 routines don't implement all the features of a real WDS1's level 2 routines.... Namely CPU RAM buffers. Which InsaneMultitasker hinted that I should implement... Fixing that may not get it to work. There are a bunch of TIPI features that need a new disk manager anyway... and I really don't think you should have to hop in and out of TIPICFG to map or unmap drives when managing files. So I'm working on something.

 

Right now you can copy from other devices into the TIPI, and you can copy amongst tipi devices.

I've just found another bug deleting from real floppy with tipi in the mix... Myarc mode can still be used to get TIPI out of your way for real DSK1 manipulations.

 

:(

 

-M@

  • Like 1
Omega-TI Quadrunner

Omega-TI

Posted
Posted

 

I've narrowed it down to "AINT" GONNA WORK" without a TIPI aware disk manager....

... There are a bunch of TIPI features that need a new disk manager anyway...

... So I'm working on something.

 

 

Since it looks like I'm gonna have to eventually replace my controller, what are the chances of making it at least DSDD 80 Track (2880 sectors) to make the added expense worth while? I'd prefer DSQD 80 Track, but TI99Dir does not go up that high... at least yet. :grin:

jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

 

Since it looks like I'm gonna have to eventually replace my controller, what are the chances of making it at least DSDD 80 Track (2880 sectors) to make the added expense worth while? I'd prefer DSQD 80 Track, but TI99Dir does not go up that high... at least yet. icon_biggrinwink.gif

 

I am extremely confused, and do not know what you are talking about... :(

 

-M@

  • Like 1
Shift838 River Patroller

Shift838

Posted
Posted

so I doubled checked my copy success that I thought i had (key word thought). I must have taken the tipi out of Myarc mode and when I did a catalog it showed DSK1 directory on the TiPi.

 

I tried to copy again today from TiPi (Latest update v027) to DSK1 and although it says it did it, it only shows a size 2 Display Fixed file. I even tried to create a oneliner basic program to make sure there was not a buffer issue and copy that but it yielded the same results.

 

The below are the log files. 1> Booted RPi3 2> Go into TIPICFG 3> set to Myarc Mode 4> Copied TELNET & TELNEU from WDS1 to DSK1. 5> Cataloged DSK1 and shows:

 

Name Size Type

 

TELNET 2 DIS/FIX

TELNEU 2 DIS/FIX

2018-08-18 18:37:54,541 TipiService : INFO     TIPI Ready
2018-08-18 18:40:11,202 TipiDisk    : INFO     Opcode 5 LOAD - TIPI.TIPICFG
2018-08-18 18:40:11,204 Pab         : INFO     opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198
2018-08-18 18:40:11,209 TipiDisk    : INFO     LOAD image size 8192
2018-08-18 18:40:12,739 TipiService : INFO     Request completed.
2018-08-18 18:40:12,954 TipiDisk    : INFO     Opcode 5 LOAD - TIPI.TIPICFH
2018-08-18 18:40:12,954 Pab         : INFO     opcode: Load, fileType: Sequential, mode: Update, dataType: Display, recordType: Fixed, recordLength: 0, recordNumber: 8198
2018-08-18 18:40:12,957 TipiDisk    : INFO     LOAD image size 5376
2018-08-18 18:40:13,914 TipiService : INFO     Request completed.
2018-08-18 18:40:14,532 Pab         : INFO     opcode: Open, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,542 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,556 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,571 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,586 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,601 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,615 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,631 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,647 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,660 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,673 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,690 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,706 Pab         : INFO     opcode: Read, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,835 Pab         : INFO     opcode: Close, fileType: Sequential, mode: Input, dataType: Display, recordType: Variable, recordLength: 80, recordNumber: 0
2018-08-18 18:40:14,865 StatusFile  : INFO     open PI.STATUS
2018-08-18 18:40:15,294 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,311 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,327 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,345 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,361 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,376 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,390 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,411 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,427 StatusFile  : INFO     read PI.STATUS
2018-08-18 18:40:15,436 StatusFile  : INFO     close PI.STATUS
2018-08-18 18:40:21,359 TipiService : INFO     TIPI Ready
2018-08-18 18:40:42,063 TipiDisk    : INFO     Opcode 0 Open - WDS1.
2018-08-18 18:40:42,064 Pab         : INFO     opcode: Open, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 0, recordNumber: 0
2018-08-18 18:40:42,082 TipiService : INFO     Request completed.
2018-08-18 18:40:42,095 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 0
2018-08-18 18:40:42,107 TipiService : INFO     Request completed.
2018-08-18 18:40:42,349 Pab         : INFO     opcode: Close, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 1
2018-08-18 18:40:42,350 TipiService : INFO     Request completed.
2018-08-18 18:40:42,358 TipiDisk    : INFO     Opcode 0 Open - WDS1.
2018-08-18 18:40:42,358 Pab         : INFO     opcode: Open, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 0, recordNumber: 0
2018-08-18 18:40:42,365 TipiService : INFO     Request completed.
2018-08-18 18:40:42,376 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 0
2018-08-18 18:40:42,385 TipiService : INFO     Request completed.
2018-08-18 18:40:42,399 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 1
2018-08-18 18:40:42,406 TipiService : INFO     Request completed.
2018-08-18 18:40:42,422 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 2
2018-08-18 18:40:42,430 TipiService : INFO     Request completed.
2018-08-18 18:40:42,446 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 3
2018-08-18 18:40:42,454 TipiService : INFO     Request completed.
2018-08-18 18:40:42,469 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 4
2018-08-18 18:40:42,477 TipiService : INFO     Request completed.
2018-08-18 18:40:42,493 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 5
2018-08-18 18:40:42,501 TipiService : INFO     Request completed.
2018-08-18 18:40:42,517 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 6
2018-08-18 18:40:42,525 TipiService : INFO     Request completed.
2018-08-18 18:40:42,541 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 7
2018-08-18 18:40:42,549 TipiService : INFO     Request completed.
2018-08-18 18:40:42,564 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 8
2018-08-18 18:40:42,573 TipiService : INFO     Request completed.
2018-08-18 18:40:42,588 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 9
2018-08-18 18:40:42,597 TipiService : INFO     Request completed.
2018-08-18 18:40:42,612 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 10
2018-08-18 18:40:42,621 TipiService : INFO     Request completed.
2018-08-18 18:40:42,636 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 11
2018-08-18 18:40:42,645 TipiService : INFO     Request completed.
2018-08-18 18:40:42,660 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 12
2018-08-18 18:40:42,668 TipiService : INFO     Request completed.
2018-08-18 18:40:42,684 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 13
2018-08-18 18:40:42,692 TipiService : INFO     Request completed.
2018-08-18 18:40:42,708 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 14
2018-08-18 18:40:42,716 TipiService : INFO     Request completed.
2018-08-18 18:40:42,732 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 15
2018-08-18 18:40:42,740 TipiService : INFO     Request completed.
2018-08-18 18:40:42,756 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 16
2018-08-18 18:40:42,764 TipiService : INFO     Request completed.
2018-08-18 18:40:42,780 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 17
2018-08-18 18:40:42,788 TipiService : INFO     Request completed.
2018-08-18 18:40:42,804 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 18
2018-08-18 18:40:42,812 TipiService : INFO     Request completed.
2018-08-18 18:40:42,824 Pab         : INFO     opcode: Close, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 19
2018-08-18 18:40:42,825 TipiService : INFO     Request completed.
2018-08-18 18:40:53,057 TipiDisk    : INFO     Opcode 0 Open - WDS1.NET.
2018-08-18 18:40:53,058 Pab         : INFO     opcode: Open, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 0, recordNumber: 0
2018-08-18 18:40:53,067 TipiService : INFO     Request completed.
2018-08-18 18:40:53,080 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 0
2018-08-18 18:40:53,092 TipiService : INFO     Request completed.
2018-08-18 18:40:53,108 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 1
2018-08-18 18:40:53,120 TipiService : INFO     Request completed.
2018-08-18 18:40:53,139 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 2
2018-08-18 18:40:53,149 TipiService : INFO     Request completed.
2018-08-18 18:40:53,165 Pab         : INFO     opcode: Read, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 3
2018-08-18 18:40:53,174 TipiService : INFO     Request completed.
2018-08-18 18:40:53,187 Pab         : INFO     opcode: Close, fileType: Relative, mode: Input, dataType: Internal, recordType: Fixed, recordLength: 38, recordNumber: 4
2018-08-18 18:40:53,188 TipiService : INFO     Request completed.
2018-08-18 18:41:05,240 LevelTwo    : INFO     set path request
2018-08-18 18:41:05,245 LevelTwo    : INFO     unit: 1, path: WDS1.NET.
2018-08-18 18:41:05,251 LevelTwo    : INFO     direct input
2018-08-18 18:41:05,256 LevelTwo    : INFO     unit: 1, blocks: 0, filename: TELNET, startblock 0
2018-08-18 18:41:07,240 LevelTwo    : INFO     set path request
2018-08-18 18:41:07,245 LevelTwo    : INFO     unit: 1, path: WDS1.NET.
2018-08-18 18:41:07,250 LevelTwo    : INFO     direct input
2018-08-18 18:41:07,256 LevelTwo    : INFO     unit: 1, blocks: 0, filename: TELNEU, startblock 0
Omega-TI Quadrunner

Omega-TI

Posted
Posted

There are a bunch of TIPI features that need a new disk manager anyway... and I really don't think you should have to hop in and out of TIPICFG to map or unmap drives when managing files. So I'm working on something.

 

 

Since it looks like I'm gonna have to eventually replace my controller, what are the chances of making it at least DSDD 80 Track (2880 sectors) to make the added expense worth while? I'd prefer DSQD 80 Track, but TI99Dir does not go up that high... at least yet. :grin:

 

 

I am extremely confused, and do not know what you are talking about... :(

 

I quickly read your message just as I was leaving this morning and ASSUMED when you mentioned a NEED FOR NEW DISK MANAGER that you were talking about coming out with... A NEW TIPI AWARE DISK MANAGER. If that is not the case, what is that "SOMETHING" you are working on?

  • Like 1
jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

Since it looks like I'm gonna have to eventually replace my controller, what are the chances of making it at least DSDD 80 Track (2880 sectors) to make the added expense worth while? I'd prefer DSQD 80 Track, but TI99Dir does not go up that high... at least yet. icon_biggrinwink.gif

I am extremely confused, and do not know what you are talking about... icon_sad.gif

 

-M@

I quickly read your message just as I was leaving this morning and ASSUMED when you mentioned a NEED FOR NEW DISK MANAGER that you were talking about coming out with... A NEW TIPI AWARE DISK MANAGER. If that is not the case, what is that "SOMETHING" you are working on?

 

We probably just have different ideas of what is responsible for what... or what 'controller' means. you seem to be calling Ti99Dir a controller... and it sort of is...

 

I'm talking about a file manager on the 4A (software) because we are talking about the problem of copying from TIPI to physical floppies. The attributes you are talking about are that of a Floppy Disk Controller (hardware) - or in the case of TI99Dir, something pretending to be a TI floppy controller for disk images.

 

File management doesn't need to know about tracks and sectors.

 

Disk formatting and duplication cares about tracks and sectors... But you won't get that from me.. cause I'm in a war against spinny things. ROFL...

 

Maybe you are trying to accomplish something else entirely... I have been wondering who really cares about copying from TIPI to physical floppies... except to run those gems that require true >10 - sector read write.

 

-M@

jedimatt42 River Patroller

+jedimatt42

Posted
  • Author
Posted

so I doubled checked my copy success that I thought i had (key word thought). I must have taken the tipi out of Myarc mode and when I did a catalog it showed DSK1 directory on the TiPi.

 

I tried to copy again today from TiPi (Latest update v027) to DSK1 and although it says it did it, it only shows a size 2 Display Fixed file. I even tried to create a oneliner basic program to make sure there was not a buffer issue and copy that but it yielded the same results.

 

The below are the log files. 1> Booted RPi3 2> Go into TIPICFG 3> set to Myarc Mode 4> Copied TELNET & TELNEU from WDS1 to DSK1. 5> Cataloged DSK1 and shows:

 

Name Size Type

 

TELNET 2 DIS/FIX

TELNEU 2 DIS/FIX

2018-08-18 18:37:54,541 TipiService : INFO     TIPI Ready
...

 

Your data matches my findings.

 

-M@

Omega-TI Quadrunner

Omega-TI

Posted
Posted

 

We probably just have different ideas of what is responsible for what... or what 'controller' means. you seem to be calling Ti99Dir a controller... and it sort of is...

 

I'm talking about a file manager on the 4A (software) because we are talking about the problem of copying from TIPI to physical floppies. The attributes you are talking about are that of a Floppy Disk Controller (hardware) - or in the case of TI99Dir, something pretending to be a TI floppy controller for disk images.

 

File management doesn't need to know about tracks and sectors.

 

Disk formatting and duplication cares about tracks and sectors... But you won't get that from me.. cause I'm in a war against spinny things. ROFL...

 

Maybe you are trying to accomplish something else entirely... I have been wondering who really cares about copying from TIPI to physical floppies... except to run those gems that require true >10 - sector read write.

 

 

Ahhh... I see what you mean! I only mentioned TI99Dir because that's the program I use to make my .DSK images for .HFE conversion for use with the Lotharek HxC. I figured if you were talking a new FLOPPY DISK CONTROLLER, I'd put in a request for as large a format as possible, but since that is not the case... never mind! :P

 

Yes, I still use some programs that REQUIRE a real floppy (format) for all functions to operate properly. My intent when getting the PEB-TIPI was to be able to still use those programs, along with some other hardware. One program (currently being worked on by someone) may eliminate the need for one of my more used programs on disk drive.

 

I'm crossing my fingers that your new FILE MANAGER will work under 4A/DOS. One irritation on the TI is having to swap cartridges whenever I need to use DM2K as it simply will not work when called directly from 4A/DOS. A loader will work, but that's extra steps slowing me down.

Shift838 River Patroller

Shift838

Posted
Posted

I know the Adafruit PiOLED - 128x32 Monochrome OLED Add-on for Raspberry Pi is used to be a status display for the TiPi. Some months back, Matt had to update the OLED library as something changed. So it makes me wonder based on the update would other OLED such as an OLED 128x64 (HERE) work with out if wired correctly to the Pi3 for status without having to hack the current tipi image?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2023 AtariAge

×
×
  • Create New...