Just wondering the general consensus on using a GOTEK device.Google HXC2001.
There is practically no documentation on them. The official site is worthless. I have a unit with a rotary knob on front that isn't even
shown on the site.
Wading through the noise, and the confusion between a 'flash drive' and 'flashing', I'm getting the impression the thing needs to be
reprogrammed (aka 'flashed') to understand a specific disk parameter
setup.
Wouldn't it be better to just keep all of the known ones stored on the
device and select the one required from a menu? Maybe that's asking too
much.
So, do I need to get programming SW, cables, etc. and go for it?
-J
On Friday, April 22, 2022 at 6:31:18 AM UTC-5, John Crane wrote:
Just wondering the general consensus on using a GOTEK device.Google HXC2001.
There is practically no documentation on them. The official site is
worthless. I have a unit with a rotary knob on front that isn't even
shown on the site.
Wading through the noise, and the confusion between a 'flash drive' and
'flashing', I'm getting the impression the thing needs to be
reprogrammed (aka 'flashed') to understand a specific disk parameter
setup.
Wouldn't it be better to just keep all of the known ones stored on the
device and select the one required from a menu? Maybe that's asking too
much.
So, do I need to get programming SW, cables, etc. and go for it?
-J
A better way to go is Lorathek which you can also google.
Randy
To flash a gotek you need a usb to ttl serial adapter:
https://www.ebay.com/itm/224493165773?hash=item3444d5dccd:g:VRoAAOSwrUBgwnrq
The plugs at the end are too big, remove them and put heat-shrink tubing on them (or wrap with tape).
You will usually need to solder header pins on the gotek.
Instructions should be on the website.
RandyForgot to specify by ends I mean the black plastic covers not the metal part.
Just wondering the general consensus on using a GOTEK device.It says "Flash Floppy' on the display.
There is practically no documentation on them. The official site is worthless. I have a unit with a rotary knob on front that isn't even
shown on the site.
Wading through the noise, and the confusion between a 'flash drive' and 'flashing', I'm getting the impression the thing needs to be
reprogrammed (aka 'flashed') to understand a specific disk parameter setup.
Wouldn't it be better to just keep all of the known ones stored on the
device and select the one required from a menu? Maybe that's asking too
much.
So, do I need to get programming SW, cables, etc. and go for it?
-J
OK some progress.Try here:
Ignore the GoTek site.
Instead look for the FlashFloppy Github site. That has useful info.
I managed to create an FF.CFG and IMG.CFG files on my usb stick.
My GoTrek tries to read it on startup - but gives error 34.
Which means it didn't find any disk images on the USB drive.
Well.. of course. It's blank, I presumed to copy over what I wanted
from my A: drive.
I guess that's not how it works. However, I'm not seeing anything about
how to create the disk images on the USB flash drive.
What format are the files? A cursory search did not find any Osborne
disk images. Perhaps someone could point the way...
-J
I had some time over lunch, so I tinkered some more...
All working now.
A couple of problems along the way...
1) Errors in the diskdefs file for cpmtools
2) FlashFloppy docs incorrectly mention they work with IMG files. They use HFE
files, as mentioned in the article.
https://www.richardloxley.com/wp-content/uploads/2019/07/Osborne-HFE-images.zip
You will need 1 or more of the above files plus IMG.CFG and FF.CFG files on your USB stick (formatted to FAT32).
Thanks all!
-John
On 4/25/22 12:54, John Crane wrote:
I had some time over lunch, so I tinkered some more...
All working now.
A couple of problems along the way...
1) Errors in the diskdefs file for cpmtools
This is unfortunately a fact of life. In fairness, there are just a
myriad of CP/M formats out in the wild.
2) FlashFloppy docs incorrectly mention they work with IMG files. They
use HFE files, as mentioned in the article.
Flashfloppy works just fine with raw sector images. However you do need
to fully define the format in the IMAGE.CFG file. The definition can be keyed a substring in the image name or, more conveniently, to the size
of the image file. Here's what I use for the Kaypro computers:
[::204800]
cyls = 40
heads = 1
secs = 10
bps = 512
interleave = 3
id = 0
# Kaypro 400kB: DSDD, 40 cyl
[::409600]
cyls = 40
heads = 2
secs = 10
bps = 512
interleave = 3
h = 0
tracks = 0-39.0
id = 0
tracks = 0-39.1
id = 10
Also, the file extension should be .DSK for raw images. HFE is much
more convenient since it has the geometry metadata included in the file,
but both will work side-by-side in the same USB stick.
Lastly, fitting the Gotek with a little LCD display makes life SO much simpler. It does take a bit of fiddling, but I've converted about a
dozen with no major issues. See the step-by-step photos of my mods here:
https://bit.ly/gotekmod
See the Flashfloppy Wiki for full details on connecting the LCD.
https://www.richardloxley.com/wp-content/uploads/2019/07/Osborne-HFE-images.zip
You will need 1 or more of the above files plus IMG.CFG and FF.CFG
files on your USB stick (formatted to FAT32).
Thanks all!
-John
On 4/25/22 2:38 PM, Steven Hirsch wrote:
Flashfloppy works just fine with raw sector images. However you do need to >> fully define the format in the IMAGE.CFG file. The definition can be keyed >> a substring in the image name or, more conveniently, to the size of the
image file. Here's what I use for the Kaypro computers:
Not my experience. I have the image config file setup. Still didn't work.
However... my files had an IMG extension. I didn't read anything about a DSK
extension until this. That could have caused my setup to fail, given the inherent fragility of the system.
I think cpmtools produces raw image files, so something like:
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
On 4/26/22 9:07 AM, John Crane wrote:
I think cpmtools produces raw image files, so something like:
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
Well... it didn't work. The DSK file was made, I used cpmcp to copy
some files to it, then tried the USB stick on the Gotek. It saw the DSK
file but gave me an error 31.
Maybe some other tool was used to create the DSK image file?
I say this as I've already found design/eng issues with cpmtools so I
regard it as 'fragile' - meaning more bugs are likely to be found.
On 4/26/22 9:07 AM, John Crane wrote:
I think cpmtools produces raw image files, so something like:Well... it didn't work. The DSK file was made, I used cpmcp to copy some
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
files to it, then tried the USB stick on the Gotek. It saw the DSK file but gave me an error 31.
Maybe some other tool was used to create the DSK image file?
I say this as I've already found design/eng issues with cpmtools so I regard it as 'fragile' - meaning more bugs are likely to be found.
On 4/26/22 13:21, John Crane wrote:
On 4/26/22 9:07 AM, John Crane wrote:
I think cpmtools produces raw image files, so something like:Well... it didn't work. The DSK file was made, I used cpmcp to
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
copy some files to it, then tried the USB stick on the Gotek. It saw
the DSK file but gave me an error 31.
Maybe some other tool was used to create the DSK image file?
I say this as I've already found design/eng issues with cpmtools so I
regard it as 'fragile' - meaning more bugs are likely to be found.
I'm not able to pull apart one of my O1s at the moment, but this should
be the correct definition for Flashfloppy IMG.CFG:
# Osborne 1: SSSD, 40 cyl
[::102400]
cyls = 40
heads = 1
interleave = 2
secs = 10
mode = fm
rate = 250
bps = 128
id = 1
This cpmtools definition works just fine on all the O1 sector images here:
# BEGIN osb1sssd Osborne 1 - SSSD 48 tpi 5.25" - 256 x 10
# Test OK - image size = 102,400, from Don Maslin's archive
diskdef osb1sssd
seclen 256
tracks 40
sectrk 10
blocksize 2048
maxdir 64
skew 2
boottrk 3
os 2.2
end
I cannot speak for the windows port of cpmtools, but the Linux and Mac
ports are quite solid.
Assuming your e-mail address is valid, I've sent you a DSK file that
should work with the Gotek.
In terms of community support, you need to be in the right place. This group is very low volume. You'd be better off calling for help at the
VCF forums or the Facebook CP/M group.
Steve
On 4/26/22 13:21, John Crane wrote:
On 4/26/22 9:07 AM, John Crane wrote:
I think cpmtools produces raw image files, so something like:Well... it didn't work. The DSK file was made, I used cpmcp to
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
copy some files to it, then tried the USB stick on the Gotek. It saw
the DSK file but gave me an error 31.
Maybe some other tool was used to create the DSK image file?
I say this as I've already found design/eng issues with cpmtools so I
regard it as 'fragile' - meaning more bugs are likely to be found.
I'm not able to pull apart one of my O1s at the moment, but this should
be the correct definition for Flashfloppy IMG.CFG:
# Osborne 1: SSSD, 40 cyl
[::102400]
cyls = 40
heads = 1
interleave = 2
secs = 10
mode = fm
rate = 250
bps = 128
id = 1
This cpmtools definition works just fine on all the O1 sector images here:
# BEGIN osb1sssd Osborne 1 - SSSD 48 tpi 5.25" - 256 x 10
# Test OK - image size = 102,400, from Don Maslin's archive
diskdef osb1sssd
seclen 256
tracks 40
sectrk 10
blocksize 2048
maxdir 64
skew 2
boottrk 3
os 2.2
end
I cannot speak for the windows port of cpmtools, but the Linux and Mac
ports are quite solid.
Assuming your e-mail address is valid, I've sent you a DSK file that
should work with the Gotek.
In terms of community support, you need to be in the right place. This group is very low volume. You'd be better off calling for help at the
VCF forums or the Facebook CP/M group.
Steve
I tried the change from2FOO0aqszy3LzdsAZZVLRlIIYtkWP1jCci2mnyJEeepGS4GqzMkfWfXI7QKO0hVB5RO01Iow7eVMYvy%2BprfdJa%2FJ%2FhsB9LodRibYqzouNt2hEtgjnNK5hjJXz9m5D5bBkVyeJ%2BEE9vk7O%2Fv7JQEgnDlmy%2BxSImE%2FA9DCA5B2NZPN2jfx979jgHLVms1hhzzsi0L0wbs%3D%7Ctkp%3ABFBMwp7Tq45g
[osb2] to [::204800]
Same Error 31
I even renamed the IMG.CFG file to IMG. and same error. However, as you suspected, the HFE files work fine. It's not even using the IMG.CFG
file. And the only thing in my FF.CFG file just rotates the display.
It seems my unit is somehow different. Not only is there bad
documentation, they changed the hardware/firmware along the way making
it more difficult to follow. Yikes!
I bought my unit on ebay a month ago. It looks like this one:
https://www.ebay.com/itm/234373137038?_trkparms=ispr%3D1&hash=item3691ba428e:g:1NkAAOSwQVhhTiCI&amdata=enc%3AAQAGAAAA0CwOsEA87vxTdC6o2FUtWAtD5Qawa1SoXo3VS03LnutJAFtzxgtW8Qcc9LYrmqGpRSY1Lm60MfCRYr9w%2B%
-J
On 4/27/22 9:11 AM, Steven Hirsch wrote:
On 4/26/22 13:21, John Crane wrote:
On 4/26/22 9:07 AM, John Crane wrote:
I think cpmtools produces raw image files, so something like:Well... it didn't work. The DSK file was made, I used cpmcp to
mkfs.cpm -fosborne1 MYDISK.DSK
may work. I'll give it a try. Thanks! -J
copy some files to it, then tried the USB stick on the Gotek. It saw
the DSK file but gave me an error 31.
Maybe some other tool was used to create the DSK image file?
I say this as I've already found design/eng issues with cpmtools so I
regard it as 'fragile' - meaning more bugs are likely to be found.
I'm not able to pull apart one of my O1s at the moment, but this
should be the correct definition for Flashfloppy IMG.CFG:
# Osborne 1: SSSD, 40 cyl
[::102400]
cyls = 40
heads = 1
interleave = 2
secs = 10
mode = fm
rate = 250
bps = 128
id = 1
This cpmtools definition works just fine on all the O1 sector images
here:
# BEGIN osb1sssd Osborne 1 - SSSD 48 tpi 5.25" - 256 x 10
# Test OK - image size = 102,400, from Don Maslin's archive
diskdef osb1sssd
seclen 256
tracks 40
sectrk 10
blocksize 2048
maxdir 64
skew 2
boottrk 3
os 2.2
end
I cannot speak for the windows port of cpmtools, but the Linux and Mac
ports are quite solid.
Assuming your e-mail address is valid, I've sent you a DSK file that
should work with the Gotek.
In terms of community support, you need to be in the right place.
This group is very low volume. You'd be better off calling for help
at the VCF forums or the Facebook CP/M group.
Steve
SUCCESS!
Steve, you were definitely looking in the right place.
The [::] tag is evidently a space for 3 params, the final being the size, which is apparently optional for my setup.
The first is a named tag. For example, [osb1] will require files to be named with osb1 as the 'middle name'.
Like: wordstar_disk.osb1.DSK
And it works with either DSK or IMG as the final extension.
All I had to do was rename my files and it all worked.
Thank you so much for pointing me in the right direction!
Just wondering the general consensus on using a GOTEK device.
There is practically no documentation on them. The official site is >worthless. I have a unit with a rotary knob on front that isn't even
shown on the site.
Wading through the noise, and the confusion between a 'flash drive' and >'flashing', I'm getting the impression the thing needs to be
reprogrammed (aka 'flashed') to understand a specific disk parameter
setup.
Wouldn't it be better to just keep all of the known ones stored on the
device and select the one required from a menu? Maybe that's asking too
much.
So, do I need to get programming SW, cables, etc. and go for it?
-J
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:37:17 |
| Calls: | 10,387 |
| Calls today: | 2 |
| Files: | 14,060 |
| Messages: | 6,416,691 |