TIImageTool on Github

[Sinphaltimus]

Wow, I'm honored ny code is being used as an example. I apologize it's not all tidy..yet.

 

I've never compiled anything (from github or any other downloadable source code source). As soon as I figure out that part, I'll be able to participate in this.

[sometimes99er]

I've never compiled anything (from github or any other downloadable source code source). As soon as I figure out that part, I'll be able to participate in this.

You can find a link in my signature to get a recent precompiled version.

 

 

 

[sometimes99er]

OK, I think I could successfully fix that. Please pull a new copy or download from WHTech or via Ninerpedia.

Excellent. Thanks.

 

I was thinking that Sinphaltimus could go from source in text file to running in emulator faster with your tool, than pasting the large program in Classic99. That's loading the resulting TIFILES-file instead of pasting.

 

 

 

 

 

[Sinphaltimus]

Now that I have a virtual floppy in my peb ...

 

 

I'm going to give this a whirl tonight.

 

Objective:

 

Save program in classic 99 to dsk format, convert dsk format in to hfe format, load on the hxc gotek usb thumb drive, load in to GoTek, run on real iron.

 

Or should I just import the extended basic text in to a newly created hfe file straight away?

 

...

[+mizapf]

Depends where you start from. Do you have the program as a plain text (e.g. from this forum), or as a TIFILES file, or as a file in the DSK image?

[Sinphaltimus]

Depends where you start from. Do you have the program as a plain text (e.g. from this forum), or as a TIFILES file, or as a file in the DSK image?

I wrote it myself, I have it as plain text extended basic and as a dsk image. I never used this tool before but I'm about to give it a go right now...

 

 

EDIT: Well it's not working for me. I cut and past in to text editor to import it and I get an error "Program too long for Program format".

And when I save from Classic 99 is doesn't add a dsk extension - timage tool doesn't recognize the format.

 

I'm kind of stuck without a clue as to what to try next or what to do.

 

Other than that, I did get a blank formatted hfe file done.

Edited October 3, 2016 by Sinphaltimus

[+mizapf]

If it is already on a DSK, just use File->New ... Floppy Image -> Set the parameters, choose HFE image as type, save the image. Open your DSK, mark the file, CTRL-C, go to the tab of the HFE image, CTRL-V. Close everything.

[Sinphaltimus]

I'm going to guess it is not a dsk. In classic99 I save dsk1.zombi and in the dsk1 folder is a zombi file.

Inside of that dsk1 folder are a few other dsk images.

I guess the contents of the dsk1 folder are not necessarily saved as dsk files. That's where my misunderstanding of thei process is taking place I suppose.

I don't know how to get my extended basic program inside of Classic99 in to a dsk or hfe for that matter.z

EDIT: OK I thought I figured it out as I did get the file to disk from the dsk1 folder of classic99, I did get the disk in to the TI and I typed old dsk1.zombi036

It paused for a really long time. I figured it was loading.

Then I get I/O error 06.

Now I'm going to hit google. I need to find a list of these kinds of errors. I think there is one in the PEB manual or DISK controller manual.

Edited October 3, 2016 by Sinphaltimus

[+mizapf]

Don't user lowercase; there is no "dsk1".

 

If you save a file in Classic99, this is supposedly a TIFILES-type file. Drag and drop it from your explorer into the HFE image in TIImageTool.

[Sinphaltimus]

Ok I got this far. To your comment above, Yes, I discovered that part in my previous comment, I chose to import file and it worked for getting the file on disk. Did not

try DnD but glad that's an option.

Here's what the problem is.

I tried everything I did earlier with one exception, I initialized the HFE as 40 track instead of 80 and it worked.

So the program and the process is working, I just have to confirm whether or not 80 track hfe images are working with my GoTek HxC or not.

I may have initialized my first HFE file incorrectly (SSDD) instead of DSSD.

AND I decided to try it before posting these comments and yes. I initialized DSSD and it all works great.

I understand now.

 

And this is freaking awesome. Thank you for this application, you have made life that much better.

I now have a quick and efficient way of getting programs from my PC to my TI and vise versa.

EDIT: - I have to tell you, you have brought so much joy to this man just now. I'm playing my Zombi game (work in progress) on real iron for the first time and it feels incredible. Thank you again for this awesome tool.

Edited October 3, 2016 by Sinphaltimus

[+mizapf]

It's a similarly pleasant experience to hear that a tool is actually helpful for someone else. So I'm really glad that it's working as it is supposed to do.

 

Since I only have limited ways to test the feature (no Lotharek/Gotek here), there could be hidden bugs; please inform me in time. And as always, especially with storage features, keep some backups.

[+mizapf]

Dear friends, I'm proud to announce another release of TIImageTool, release 2.4 of December 2016. I worked hard to finish this release right in time for Christmas, just as promised.

 

The good thing about this is that there are again lots of new features, and I hope there's something for you, too. The bad thing (or maybe good?) is that now, TIImageTool is basically complete. It contains everything I ever wanted it to have, and I have no further plans for additions. There will be fixes, of course, for quite some time, but I don't have anything more to add or to improve. It does not happen too often that you can say you have finished a project, does it?

 

So let's have a look at the features:

 

• Open EMULATE files: A special kind of file used with the HFDC. You can create such a file from a complete floppy disk and have the HFDC emulate DSK1 by one of these files. This makes it quite easy to work with programs that require to be loaded from DSK1. TIMT can now create such files from floppy images, and you can activate or deactivate them by the context menu.
• Sector editor: You may want to fix some error on your image; you can certainly do this with sector dumps with a sector editor tool. The now built-in sector editor works on top of the format layer in TIMT, i.e. you can edit sectors of images of any format - sector dumps, track dumps, CHDs. You can even repair your HFE (Lotharek) images which is pretty impossible with an external sector editor.
• Rename volumes: Change the name of your floppy or hard disk image (not the file name of the image but the disk name)
• Properties dialog is organized by tabs
• Show RLE-128 images (contribution of HackMac)
• Fixes: double console output, marking in directory view
• Drag-and-drop: You get a choice window at the drop event, asking you whether you want to move or copy the file - unless you already pressed Shift or Ctrl
• Base address for plain dumps: When you show hexdumps of your binary files (like ROMs) you can specify the base address, just like you do with the Disassembler. This is quite useful because you get the proper addresses in the dump
• Compact Flash handling: I found a way to get a support to read/write compact flash cards. TIMT will spawn a process that runs the /usr/bin/dd program (or the DD.EXE port for Windows), allowing you to read and write from an external drive.
• CF7 handling: By using the CF read/write feature, you can actually create a backup of your CF7 card on your PC, but also work with the enclosed volumes. There is no more need for cf2dsk or dsk2cf; all is done inside TIMT.
• Yes, and finally: TIImageTool becomes international. Ja, es gibt schon eine komplette deutsche Übersetzung, et si on trouve quelqu'un entre nous parlant le Français mieux que moi, tu es invité a m'aider avec la traduction.

 

As always, get the release from my server: http://www.mizapf.eu/files/tiimagetool.zip

or from WHTech: http://ftp.whtech.com/pc%20utilities/tiimagetool.zip

 

or clone my Github repository at https://github.com/mizapf/tiimagetool

 

With this lot of new additions, bugs and errors are unavoidable. Please report them to me so I can fix them.

 

***** Merry Christmas! *****

[atrax27407]

Thanks, Michael, I have a working version once again!!

[+Ksarul]

Thank you Michael! I think one bug I recently found in the previous version needs to be reported yet (and you may have found it yourself and fixed it already). When copying a group of files to an HFE image, all files copy over flawlessly (and catalof perfectly in TIMT). When viewing that image in a Lotharek drive, however, their is an off-by-one error, in that the last file copied won't show up. It turns out that the pointer to the file header is missing. I go in with DSKU on the TI side with the image mounted and sector edit the HFE to add the final pointer and all is good, so it is just a minor added step when copying a lot of files into an HFE image. As noted, the data is always there in the right place, just the sector pointer alerting the disk manager to the existence of the last program header data sector is missing.

[Shift838]

Michael,

 

does this new code have the 38400 code enable in it too?

[+mizapf]

@Shift838: I removed the limitation was some time ago, so indeed, you should be able to use the bridge at higher rates than 19200.

 

@ksarul: If there is an error with sector management, this should happen with all formats, not only HFE. The image format is the lowest layer, that is, it should only bother with writing bits or bytes. What you found sounds like a higher-layer issue to me; the only way it could be a low-layer one after all is if it fails to commit some changes to the image. Please try to reproduce the problem with the current version. I actually fixed an issue with file selection in the directory views, so maybe this is related.

[RXB]

Hmm none of the downloads work with Windows 10?

 

The link for running under Windows is a DEAD LINK!

Edited December 25, 2016 by RXB

[+mizapf]

I suppose you don't want the Github source code, so both other links from my posting above should download "tiimagetool.zip", which you have to unzip to use. Start the jar file inside by double click. Remember to install a Java Runtime Environment 1.7 or 1.8 before.

[atrax27407]

The link and the program worked for me on my WIN 10 system.

Edited December 25, 2016 by atrax27407

[+mizapf]

By the way, I would be interested to hear from a CF7 user whether the new features of TIMT do their work as promised.

[Sinphaltimus]

I have an issue and maybe I'm nto using the latest version of TIImageTool.

 

From TI99DIR I access my CF card for the nano.

I select anyone of the 1600 sized dsk file and copy to local hard disk.

When i try to open the dsk file in TIImageTool, I get an error that states:

UNKNOWN FILE FORMAT or Image Corruption.

[+mizapf]

See other thread. In order to open 1600-sector images you need the latest TIImageTool. They are now supported as "CF7 volumes", not as floppy images since there is no floppy disk with 1600 sectors.

[RXB]

Do I have to download some special tools in Windows to make TI image tool to work?

[+mizapf]

You only need a current Java Runtime Environment. If you don't need Applet support, please review your browser plugins and remove or deactivate them after you installed the Java package.

Edited May 14, 2017 by mizapf

[iKarith]

This is not a major new release; I just installed a repository for TIImageTool on Github:

 

https://github.com/mizapf/tiimagetool.git

 

For building you just clone this repository, get a recent JDK, ant, and a copy of RXTXcomm.jar. Build file is included.

 

Being not a java developer, may I just resurrect this thread (I'm neglecting the forum again...) to say THANK YOU for taking the time to explain even in brief how you build this thing? The one thing I've discovered about projects written in Java is that the idea that anybody else on the planet might ever want to build your jar files on their system is at best an afterthought.

 

I've been banking my head against AppleCommander off and on for a few weeks now.