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

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.
> 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
Google HXC2001.

A better way to go is Lorathek which you can also google.

Randy

On 22/04/2022 10:59 pm, Randy McLaughlin wrote:
> 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.
>> 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
> Google HXC2001.
>
> A better way to go is Lorathek which you can also google.
>
>
> Randy

If its not already, you need to flash it with FlashFloppy, thats free.
So check out https://github-wiki-see.page/m/keirf/FlashFloppy/wiki

I have a few of these and most of my vintage computers have them running.
Full support also on their FB page
https://www.facebook.com/groups/flashfloppy

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.

Randy

On Friday, April 22, 2022 at 10:10:31 AM UTC-5, Randy McLaughlin wrote:
> 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.
>
>
> Randy
Forgot to specify by ends I mean the black plastic covers not the metal part.

Randy

The display on mine says "Flash Floppy V 3.2" So evidently it is
configured to emulate a drive?

The Osborne doesn't recognize it as a drive. I tried the "configuration
setting" - all that did was turn the display upside down and now it
won't go back to the way it was.

This is such a cryptic device.

-John

On 4/22/22 6:31 AM, John Crane wrote:
> 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
It says "Flash Floppy' on the display.

OK some progress.
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

On Sunday, April 24, 2022 at 9:15:58 PM UTC-5, John Crane wrote:
> OK some progress.
> 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
Try here:

https://www.richardloxley.com/2018/04/27/osborne-restoration-part-16-transferring-cpm-software/

Randy

Oh that's just insane - look at that diagram!
Flashfloppy says it takes IMG files, so maybe just use cpmtools?

At any rate, that's my starting point. However, it's buggy.
I kept getting 'Invalid OS type' errors using mkfs.cpm.
After a little troubleshooting, I found a couple of errors in the
diskdefs file in /etc where the version number had extra spaces
appended. Removed the spaces and it makes the image file.
I'll make a few sample images and test them this evening. I'll keep
everyone posted.

-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.

A shortcut to pre-made Osborne1 HFE disk images:

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:
> 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.

It was not a technical typo. Excess spaces before the newline char
confused the program. Either data error, or program unable to deal with it.
>
>> 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:
>

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.

> [::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.
>
>

Mine came with an OLED display and a rotary knob I can twirl to select
an image file. It shows the name of the file in the little display.

>> 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
>>
>>
>

FATE is a curious thing...

I spend all that time replacing my B: drive with a fancy new GoTek, do
the work to get it usable, get a 3d printed fascia to fit the Osborne,
start copying over files from diskettes to the new Gotek in the Osborne
and then... my A: drive starts to fail.

son of a ....

-J

I'll have to look at it later. I can (probably) handle it.
Meanwhile, I'm content to boot from the Gotek in B: via the double quote
keyboard trick.

On 4/26/22 01:16, John Crane wrote:
> 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.

Raw images must carry a .DSK extension AFAIK. That's the way I typically use
my Goteks across my various systems. Currently:

Kaypro 10
Tandy Model 16B
AT&T 7300 / UnixPC
Tandy Model 4
Heath H89 (soft-sector controller)
Xerox 820II
Lobo Max80
Several ISA bus IBM clones

and maybe a couple of others that aren't sitting at the top of my head.

I would agree with you that documentation is somewhat scattered, but all the
necessary information is there if you dig. The community is also good about
jumping in with answers.

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.

John, it's a finicky setup. I managed to get them working using a funky method. Read a floppy and create a DSK. Once the DSK file is created, examine it with IMD. Get the tracks and sectors for the image, then use those as input for the IMG.CFG file. The most important step, I found, was to convert the DSK to IMG, get the exact byte count of the img file, and use that size in the IMG header for that disk image (there can be multiple definitions). I have it working on Cromemco, CCS, and Compupro. If you need to file I can send them to you. I may be able to find my notes on the steps. Make sure you also have the number of heads correct and the number of directory tracks correct. The directory stuff should not give you an error 31, however, but just a garbage directory.

I asked so many folks for help, everyone had suggestions but none of them worked. When I asked the FlashFloppy folks, I mostly got "just do this and this" but no other detail. It's like they expect you to know all of the details inbetween. I put the Goteks in the chassis with the covers on, and no cables are required except for the monitor so it looks clean.

Once you the bootable image, adding files with cpmtools should be easier. It's actually very flexible and nice, but the same issue when asking for help - "you should know that" or posts with fragments of the diskdef file with no explanation of how and why. Took me several days on Windows but managed to slog through it. Despite it's pervasiveness and popularity, I received very little useful advice from the community.

--Steve

On Tuesday, April 26, 2022 at 1:21:30 PM UTC-4, John Crane wrote:
> 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 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:
>>    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.
>

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

Steve,
Thanks for sending the DSK file.
Unfortunately, it also gave an error 31.

I was able to see some odd data with cpmls:

john@cygnus:~/osborne$ cpmls -f osborne1 O1CPMS.DSK
10:
\.ran
\_______.___

13:

\.e
john@cygnus:~/osborne$

My cpmtools diskdef for the Osborne1 is:
# Osborne 1
diskdef osborne1
seclen 1024
tracks 40
sectrk 5
blocksize 1024
maxdir 64
boottrk 3
# os 2
os 2.2
end

And my IMG.CFG file on my USB stick is the following:
# flashfloppy/GOTEK/Osborne 1 - SSDD 48 tpi 5.25" - 1024 x 5
[osb2]
cyls = 40
heads = 1
secs = 5
interleave = 1
bps = 1024
id = 1
#rpm = 360
rpm = 300
rate = 250
mode = mfm
iam = no

The above setup only seems to work with HFE files.
And I do have the double density upgrade. Maybe that was the error in
reading your file. Could it have been for single density?

And thanks for the recommendations. I think I'll poke around the VCF
Forums. I quit FB years ago for security and privacy concerns. It's
just too Orwellian for my taste.

There is also this fellow that has a roundabout way of using HFE files:

https://www.richardloxley.com/2018/04/27/osborne-restoration-part-16-transferring-cpm-software/

I suppose it's bearable with shell scripts. It just seems so
inefficient though.

-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:
>>>    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.
>>
>
> 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 from
[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%2FOO0aqszy3LzdsAZZVLRlIIYtkWP1jCci2mnyJEeepGS4GqzMkfWfXI7QKO0hVB5RO01Iow7eVMYvy%2BprfdJa%2FJ%2FhsB9LodRibYqzouNt2hEtgjnNK5hjJXz9m5D5bBkVyeJ%2BEE9vk7O%2Fv7JQEgnDlmy%2BxSImE%2FA9DCA5B2NZPN2jfx979jgHLVms1hhzzsi0L0wbs%3D%7Ctkp%3ABFBMwp7Tq45g

-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:
>>>    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.
>>
>
> 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!

-J

On 4/28/22 7:34 PM, John Crane wrote:
> I tried the change from
> [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%2FOO0aqszy3LzdsAZZVLRlIIYtkWP1jCci2mnyJEeepGS4GqzMkfWfXI7QKO0hVB5RO01Iow7eVMYvy%2BprfdJa%2FJ%2FhsB9LodRibYqzouNt2hEtgjnNK5hjJXz9m5D5bBkVyeJ%2BEE9vk7O%2Fv7JQEgnDlmy%2BxSImE%2FA9DCA5B2NZPN2jfx979jgHLVms1hhzzsi0L0wbs%3D%7Ctkp%3ABFBMwp7Tq45g
>
>
>
> -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:
>>>>    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.
>>>
>>
>> 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/28/22 21:33, John Crane wrote:
>
>
> 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!
>

Great news! A simple '::204800' should have been sufficient - PROVIDED there
were no other stanzas using that designation. But, either way I'm happy to
hear you've solved it. Now you have a direct means for moving files in and
out of the image file without an additional format conversion.

On Fri, 22 Apr 2022 06:31:15 -0500, John Crane
<john_crane_59@yahoo.com> wrote:

>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

Did you ever see these?
https://github.com/keirf/flashfloppy/tree/master/examples/Host

Scott