Image Map Image Map
Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29

Thread: ND-110 computer

  1. #21
    Join Date
    Mar 2011
    Location
    Norway/Japan
    Posts
    858

    Default

    That is probably just a warning that can be ignored, and it'll go away if you re-dump the program. The ftn program was probably dumped on an earlier version of SINTRAN, before certain aspects of the 1bank/2bank stuff was changed. At least if the compiler appears to work it should be OK. Try a 'help' command.

    -Tor

  2. #22
    Join Date
    Aug 2009
    Location
    Oslo, Norway
    Posts
    1,167
    Blog Entries
    3

    Default

    I haven't had time to fire up SINTRAN yet; recent upgrades to my apartment made the machines inaccessible (ok, they were just stored away) for a time.
    But I wondered one thing: cna I use the COPY-FILE command to copy floppies?
    the floppy device (floppy-device 1) has a file name FLOPPY-1:;1
    So (in theory at least), I could just insert a floppy, close the drive and do
    Code:
    @COPY-FILE "destination:data", FLOPPY-1
    and SINTRAN III would copy the contents of the floppy in the drive to the new file destination:data
    Or would that fail (for reasons I do not know yet)?
    Torfinn

  3. #23
    Join Date
    Mar 2011
    Location
    Norway/Japan
    Posts
    858

    Default

    That will not work I believe, I think it'll just create a copy of the device file itself, not the content of the floppy. But you could try it of course, in case I'm wrong.

    -Tor

  4. #24
    Join Date
    Aug 2009
    Location
    Oslo, Norway
    Posts
    1,167
    Blog Entries
    3

    Default

    Well, I tried it
    Code:
    @copy-file "nd-4:data",floppy-1
    It started, and for a while things were looking good. It read from the floppy a bit, paused (writing to the hard drive?) and repeated.
    But after a while it started filling my screen with invisible characters. I did this from a serial terminal, so I went over to the console, to see if I could figure out what it the machine was doing. But the console screen started filling with the character "P". After a few seconds, I used the STOP button on the Operator panel to end the madness.

    After having started SINTRAN again, I checked the file:
    Code:
    MINI>@fi-st nd:d
    OUTPUT FILE: 
    FILE 112 : (PACK-ONE:SYSTEM)ND-4:DATA;1
               (INDEXED FILE)
               PUBLIC ACCESS : READ
               FRIEND ACCESS : READ, WRITE, APPEND
               OWN ACCESS : READ, WRITE, APPEND, COMMON, DIRECTORY
               OPENED 1 TIME
               CREATED 19.39.15  OCTOBER 7, 2000
               OPENED FOR WRITE 19.39.15  OCTOBER 7, 2000
               154 PAGES , 315392 BYTES IN FILE
    I haven't checked the contents yet, because I had trouble getting kermit to work. Along the way, it seems like two of the terminal ports on the Satellite died too. I just hope that nothing more dies in this old machine.
    Torfinn

  5. #25
    Join Date
    Mar 2011
    Location
    Norway/Japan
    Posts
    858

    Default

    Hm, 154 pages? That's promising, if what you tried to copy was an 8" ND floppy.. because it's exactly 154 pages. You do have my floppy image dumping tool, don't you? If you get that file copied over to your BSD box you should be able to check it if so.

    -Tor

  6. #26
    Join Date
    Aug 2009
    Location
    Oslo, Norway
    Posts
    1,167
    Blog Entries
    3

    Default

    Yes, I have your tool (it is a great tool - thanks!); and I plan on using that to check out the image when I get to it.
    Torfinn

  7. #27
    Join Date
    Aug 2009
    Location
    Oslo, Norway
    Posts
    1,167
    Blog Entries
    3

    Default

    Thankfully, the serial comms problem was just user error (hint: it pays off to realize which machine you are on when using the 'cu' command, and it also helps to use 'ssh -e none ...' if connecting from a remote machine).
    Today I got the file off the ND machine and onto my FreeBSD workstation.
    Initial tests doesn't look like the @file-copy command was doing perfect:
    Code:
    tingo@kg-v2$ ndfs -V
    ndfs: Sintran Filesystem tool version 1.1
    tingo@kg-v2$ ndfs -i nd-4.data
    Directory name            : ND-10523D-PART4
    Object file index pointer : 150 SI: 0x1 (indexed)
    User file index pointer   : 152 SI: 0x1 (indexed)
    Bit file pointer          : 72 SI: 0x0 (contiguous)
    No. of unreserved pages   : 1
    Error reading page 2818615296: No error: 0
    tingo@kg-v2$ ndfs -t nd-4.data
    Directory name            : ND-10523D-PART4
    Object file index pointer : 150 SI: 0x1 (indexed)
    User file index pointer   : 152 SI: 0x1 (indexed)
    Bit file pointer          : 72 SI: 0x0 (contiguous)
    No. of unreserved pages   : 1
    Error reading page 2818615296: No error: 0
    Tor, let me know if you want me to run more tests, or if you want to have a copy of the file.
    Last edited by tingo; October 16th, 2012 at 11:30 AM. Reason: fixing speliing errors...
    Torfinn

  8. #28
    Join Date
    Mar 2011
    Location
    Norway/Japan
    Posts
    858

    Default

    Feel free to send me a copy of the file, I'll take a look at it.
    The directory name indicates that it may possibly be the fourth part of a multi-floppy volume though.. and if so, it's basically a tape written to a set of floppies. Those can also be extracted, but you'll need all four (or more) floppies.

    -Tor

  9. #29
    Join Date
    Aug 2009
    Location
    Oslo, Norway
    Posts
    1,167
    Blog Entries
    3

    Default

    Done (You've got mail).
    Actually, the contents of that floppy is well known (to me at least), it is the fourth floppy in the ND-100 Test Programs set.
    Code:
    MINI>@dir-stat nd,,
    
    
    DIR INDEX 1 : FLOPPY-DISC-1 UNIT 0 : ND-10523D-PART4
          1 PAGES UNRESERVED AND 44 PAGES UNUSED OUT OF 154 PAGES
          MAXIMUM UNUSED CONTIGUOUS AREA ON DIRECTORY 44 PAGES
    and the files:
    Code:
    MINI>@l-fi (nd:f-u),,
    FILE 0 : (ND-10523D-PART4:FLOPPY-USER)DSERV-1395A:BPUN;1
    FILE 1 : (ND-10523D-PART4:FLOPPY-USER)ECCTEST-2224B:BPUN;1
    FILE 2 : (ND-10523D-PART4:FLOPPY-USER)PARAL-BYTE-1942C:BPUN;1
    FILE 3 : (ND-10523D-PART4:FLOPPY-USER)PASCAN-2226A:BPUN;1
    FILE 4 : (ND-10523D-PART4:FLOPPY-USER)RTC-12-1902B:BPUN;1
    FILE 5 : (ND-10523D-PART4:FLOPPY-USER)TANB-MAG-1559H:BPUN;1
    FILE 6 : (ND-10523D-PART4:FLOPPY-USER)TECOD-1451E:BPUN;1
    FILE 7 : (ND-10523D-PART4:FLOPPY-USER)TET2200-A:BPUN;1
    FILE 8 : (ND-10523D-PART4:FLOPPY-USER)TNCT-2039B:BPUN;1
    FILE 9 : (ND-10523D-PART4:FLOPPY-USER)UNIVERSAL-DMA-B:BPUN;1
    FILE 10 : (ND-10523D-PART4:FLOPPY-USER)VERSATEST-C:BPUN;1
    I thought it best to use a floppy with known contents, just in case I was lucky and the copy operation worked.
    Torfinn

  10. #30
    Join Date
    Mar 2011
    Location
    Norway/Japan
    Posts
    858

    Default

    The image appears to only be a dump of the memory bank of the account, with some (very little) of it filled in with some data from the floppy.
    So it doesn't seem to be possible to copy an image that way.

    I think I mentioned before that it's pretty easy to write a copy program in Fortran to do this. It needs very little, just a loop with calls to MON 144 (DeviceFunction/MAGTP) and MON 120 (WriteToFile/WFILE).

    I can write one to do the job, although obviously I have no machine to test it on - only my emulator (I started writing floppy driver support into my emu because I want to run my old CP/M copy program, but it's on the backburner for now due to other obligations).
    Now I'm about to go on mission for quite some time, but I can write that program when I'm back.

    -Tor

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •