Jump to content
IGNORED

tiimagetool


dhe

Recommended Posts

I've been playing with TI ImageTool - it's a really nice tool, with great documentation.

 

Last night I wanted to test a disk image for errors/problems/bad things. It has a really nice check disk feature, and even offers to repairs errors that it finds, and gives you the option to save to a log file.

 

So, when working under linux, I usually start a *.jar file from the command line with: javaws {something}.jar. It would appear Windows 10 doesn't like you to do that, and instead prefers that you just double click on the jar file.

 

javaws - WILL tell you if your Java is out of date, warn you of your potential demise if you don't update immediately and takes you to the updater.

 

Dano

  • Like 1
Link to comment
Share on other sites

In my case (since I am likewise a big fan of TI Image Tool), I launch TI Image Tool on Windows 10 (always without issue) via the following command:

 

start javaw -jar "C:\TI99\Image Tool\tiimagetool.jar"

 

Part of the reason for using this command is that I want to be able to associate relevant file types with the application. 

 

To do that I've got a Batch file containing the following:

 

@echo off
start javaw -jar "C:\TI99\Image Tool\tiimagetool.jar" %1

And that's associated with relevant file types.  So I can just double click, say, a .cf7 file to open it in TI Image Tool.

  • Like 2
Link to comment
Share on other sites

  • 1 year later...

I'm trying to open a disk image.

image.png.0e2a0a05fcc075833c71708902464c23.png

 

Bootdisk1.hd - is seen just fine and opens.

 

image.png.eb99c222228286f95faa0cae01aedfe6.png

 

When I go to open genos7boot.hd,

I get:

  image.png.8736323c836d9b9074c210c5902b63b2.png

 

Followed up with:

image.png.2466540a570bdb9850c2558c20316f1c.png

 

Genos7boot.hd seems to check out with chadman:

D:\mame>chdman.exe info -i  genos7boot.hd
chdman - MAME Compressed Hunks of Data (CHD) manager 0.239 (mame0239)
Input file:   genos7boot.hd
File Version: 5
Logical size: 20,152,320 bytes
Hunk Size:    4,096 bytes
Total Hunks:  4,920
Unit Size:    256 bytes
Total Units:  78,720
Compression:  none
CHD size:     327,680 bytes
Metadata:     Tag='GDDD'  Index=0  Length=33 bytes
              CYLS:615,HEADS:4,SECS:32,BPS:256.
Metadata:     Tag='GDDI'  Index=0  Length=37 bytes
              IL:4,CSKEW:0,HSKEW:0,WPCOM:-1,RWC:-1.
Metadata:     Tag='GDDI'  Index=1  Length=45 bytes
              GAP1:16,GAP2:3,GAP3:18,SYNC:13,HLEN:5,ECC:-1.

 

image.png.e3b30bcce6663ca3034ebd7f2e1a02eb.png

 

The image does boot, dir, etc.

 

Anyone know what I'm doing wrong?

Link to comment
Share on other sites

It is interesting that is says that the genos7boot.hd has floppy disk size. What is the file size?

 

This may mean that I have to modify the file type detection. For now you should be able to increase the file size by storing some more content in it; the CHD file will expand appropriately, and the wrong detection should go away.

Link to comment
Share on other sites

hum, never seen that error with windows and I have used the TIMP a lot recent with Geneve and .hd

have you run a 'check file system' on the .hd? I have had .hd get all kinds of weird errors when I would copy over some bad files from other disk using TIMP. just yesterday TIMP actually locked after I copied a series or corrupt files to an .hd from another .dsk.

Edited by hloberg
Link to comment
Share on other sites

327680 bytes happen to be the size of a sector dump image (DSK) with 40 tracks, 2 heads, and 16 sectors, i.e. the double density disks on the TI-99/8. Thanks for this heads-up, I'll have to change that in the next version by first testing for CHD (by looking for the "MComprHD" string), then for the other formats.

 

Addition: The funny thing is that in TIMT I never expected that I could mix up a floppy image and a hard disk image, because the HD image should always be much bigger. However, the CHD format does not store empty hunks (blocks), so in a mostly empty state, the HD may indeed be smaller than a DSK. When you open an image file, the available formats are checked one after another, and the first one that could match is picked. Since the sector dump format does not offer any metadata, I can only check for the file size, and it must be a multiple of 9*256 bytes (or 16*256 for this DD format). The solution, as said, is to swap the order of the format detection, as the CHD format has metadata, and begins with the "MCompHD" string (which is not on DSKs).

  • Like 3
Link to comment
Share on other sites

  • 4 weeks later...

I have a couple of Hard Drive Images (under MAME) - I'd like to be able to get a directory listing either at the root level or recursively and copy the results in to the windows clip board as text or dump to a text file, that I can later uses the PC to manipulate.

 

I've read the docs, and can't come up with how to do that. Maybe it's my hang up, because most of the commands I'm seeing are talking about copying files, not so much copy text or dump directories to a file?

Link to comment
Share on other sites

Use the scripting functionality.

 

java -classpath tiimagetool.jar de.mizapf.timt.CommandShell dir myharddisk.hd

 

creates a verbose listing of the root directory.

 

java -classpath tiimagetool.jar de.mizapf.timt.CommandShell dir myharddisk.hd ASM.BENCH

 

creates a verbose listing of the BENCH subdirectory of the ASM subdirectory of the root directory.

 

java -classpath tiimagetool.jar de.mizapf.timt.CommandShell ls myharddisk.hd [subdir] 

 

creates a simple listing of the files and directories (subdir specification as above).

 

java -classpath tiimagetool.jar de.mizapf.timt.CommandShell lsf myharddisk.hd [subdir] 

 

like ls, but appends a ".d" for subdirectories, and ".t" for DIS/VAR 80 files.

 

If you want something recursive, you should use the bash in Linux or WSL, or create something with another scripting language that first creates an lsf listing, filters for the .d entries, and calls dir for each one.

 

Example:

 

$ java -classpath tiimagetool.jar de.mizapf.timt.CommandShell dir ~/mame/disks/hd/maindisk.hd  ASM  
Volume in HDS1 is named MAINHD, total sectors: 507904, AU size: 8, CHD image
Directory of HDS1.ASM

Filename   Size Type     Length P F Created              Updated
-------------------------------------------------------------------------------
BENCH         8 Dir        2048    2021-02-12 12:16:26  
DIV           8 Dir        2048    2021-02-12 12:16:26  
DOCS          8 Dir        2048    2021-02-12 12:16:26  
EXTERN        8 Dir        2048    2021-02-12 12:16:26  
FRACG         8 Dir        2048    2021-02-12 12:16:26  
FRACGTI       8 Dir        2048    2021-02-12 12:16:26  
FRACT         8 Dir        2048    2021-02-12 12:16:26  
FRACTI        8 Dir        2048    2021-02-12 12:16:28  
LOADER        8 Dir        2048    2021-02-27 01:39:16  
SPEEC         8 Dir        2048    2021-02-12 12:16:28  
SPEEC12E      8 Dir        2048    2021-02-12 12:16:28  
SPEEC13       8 Dir        2048    2021-02-12 12:16:28  
SPEECODER     8 Dir        2048    2021-02-12 12:16:28  
TCPIP         8 Dir        2048    2021-02-12 12:16:28  
TEST          8 Dir        2048    2021-02-12 12:16:28  
XMODEM        8 Dir        2048    2021-02-12 12:16:28  
CIB0          5 Dis/Var      80                                               
FSUB,S       96 Dis/Var      80     1992-07-22 16:16:20  1992-08-26 00:13:34  
FSUB_S       90 Dis/Var      80     1993-08-01 01:24:02  1993-08-03 12:17:24  
SAVE         12 Dis/Fix      80     1991-10-12 14:12:18  1991-10-12 14:12:26  
TGRMAUS      10 Dis/Fix      80     1993-04-08 16:29:06  1993-04-08 19:12:06  
TGRMAUS1     10 Dis/Fix      80     1993-04-08 19:23:50  1993-04-08 19:24:06  
TMAUS         7 Dis/Fix      80     1992-12-20 01:52:42  1993-04-08 14:32:30  

230 sectors used in 7 files and 16 directories,
94978 sectors used, but not in this directory,
412696 sectors free

Link to comment
Share on other sites

Here is a listing sample for "lsf" for the same directory:

$ java -classpath tiimagetool.jar de.mizapf.timt.CommandShell lsf ~/mame/disks/hd/maindisk.hd ASM
BENCH.d
DIV.d
DOCS.d
EXTERN.d
FRACG.d
FRACGTI.d
FRACT.d
FRACTI.d
LOADER.d
SPEEC.d
SPEEC12E.d
SPEEC13.d
SPEECODER.d
TCPIP.d
TEST.d
XMODEM.d
CIB0.t
FSUB,S.t
FSUB_S.t
SAVE
TGRMAUS
TGRMAUS1
TMAUS

  • Thanks 1
Link to comment
Share on other sites

I just hacked together a recursive directory lister for bash.

 

#!/bin/bash 
# Recursive directory lister for use with TIImageTool
 

# Before use, check the path of TIMTJAR
TIMTJAR=/home/user/timtdir/tiimagetool.jar
CMDSHELL=de.mizapf.timt.CommandShell

showdir() {
  # local is important as we do a recursive call
  local BASE=$2

  # Collect all subdirectories; those end with ".d"
  SUBDIRS=`java -classpath $TIMTJAR $CMDSHELL lsf $1 $BASE | grep "\.d"`

  # Do the verbose listing of the current directory
  java -classpath $TIMTJAR $CMDSHELL dir $1 $BASE

  # Add a period if we are already in a subdirectory
  if [ -n "$BASE" ]
  then  
     BASE=$BASE"."
  fi

  # Loop over the directory entries
  for entry in $SUBDIRS
  do
     # Recurse
     # Strip off the ".d" suffix
     showdir $1 $BASE${entry%%\.d}
  done
}

showdir $1


 
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

  • 4 months later...

@mizapf many years ago @9640News put together a HD of Geneve software.

Since chkdsk on the Geneve isn't a super extensive checking tool, I decided to try TI Image Tool's check drive utility.

 

It really didn't seem happy ;)

 

I love the logging feature.

 

Do you have any thoughts of why so many errors?

 

I have a copy of the drive pre and post fix.

 

 

hds2_fixes

Link to comment
Share on other sites

Maybe start with a look at those files that are "likely broken". This is the case when the files contain sectors that look empty (00...00) or unused (filled with E5 or so). This does not necessarily mean they are broken, but just "likely".

 

You can see it when you double-click on such a file, or you can select "View plain dump".

  • Like 2
Link to comment
Share on other sites

  • 9 months later...

I had some good progress the last days; the result will be called "TIImageTool 3". The primary goal is a rework of the lower layers to allow for easier conversions with the introduction of a menu item "Save as" and an Undo/Redo feature, so you will create a new disk image within the tool and then at the end decide whether it will be saved as DSK, for PC99, or as HFE (Lotharek/Gotek).

 

The point is that I have to finish that first to get to a stable base, then I can continue with those enhancements you mentioned. I don't want to work on a stale branch and then port everything to the new branch.

 

I'll let you know when it is ready to be used.

  • Like 4
Link to comment
Share on other sites

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...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...