Hi Jeff,
I've put the new firmware on but I'm still getting the same problems.
I thought I'd try a few things while I had the amiga set up for the firmware upgrade.
I dug out my old AmigaOS floppies and thought I would try making some copies onto the SD card from my originals.
After booting the Amiga up with WB1.3 (one which I'd had no setpatch releated problems with) I mounted an image on the SD card and formatted the disk.
Everything seemed okay, so I ran the diskcopy command to copy from df3: to df0:
It failed the verify on the first track.
I'm really struggling to figure out whats wrong here, whether its the Amiga itself, the 060 card, the OS, the SD card, the firmware, I just don't know.
I have noticed that someone else has posted in here using the HxC with a A4000 desktop and looks to have had more success than me, so I'm going to ask him how he's got along.
Any ideas or things you want to try, please let me know. Cheers for the help so far.
Any chance you could send me the older 1.6 firmware just to rule out?
Cheers
Mr.O
Having a problem with a new rev F model
Re: Having a problem with a new rev F model
Email sent with the old firmware.
Waiting for feedback.
Waiting for feedback.
Re: Having a problem with a new rev F model
Hi Jeff,
Thanks for sending me that so quickly.
I'm having a lot more success with this firmware, I've only tested a few things but I'm currently sat in Workbench 3.9 with the latest setpatch loaded and I can mount and read floppies no problem at all.
I'll carry on testing stuff and feedback all I find.
Cheers
Mr.O
Thanks for sending me that so quickly.
I'm having a lot more success with this firmware, I've only tested a few things but I'm currently sat in Workbench 3.9 with the latest setpatch loaded and I can mount and read floppies no problem at all.
I'll carry on testing stuff and feedback all I find.
Cheers
Mr.O
...Re: Having a problem with a new rev F model
Can you send me the disk image with this famous "setpatch" ?
Re: Having a problem with a new rev F model
I just sent to you some more firmware to test.
Can tell me which one seem to have the issue ?
thanks by advance
Can tell me which one seem to have the issue ?
thanks by advance
Re: Having a problem with a new rev F model
Hi Jeff,
I've been through the firmwares you sent me and heres what I found..
1.6.0
Boot from WB3.1 floppy: Boots correctly, able to navigate around disk without read errors
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, everything worked fine.
Boot to WB3.9: Floppys are mounted correctly, able to navigate around them without read errors
tried copying files, everything worked fine
tried diskcopy df3: df0: (physical floppy to image) failed to verify track 0
1.6.2
Boot from WB3.1 floppy: Boots correctly, able to navigate around disk without read errors
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, threw 1 write error and produced later checksum errors on reading and deleting file.
Boot to WB3.9: Floppys are mounted correctly, able to navigate around them without read errors
Formatted an existing .hfe file successfully
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, threw lots of write errors but was able to delete the file.
Reads everything I've tried without errors.
1.6.3
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.4
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.5
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.6
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
As it stands I've left 1.6.0 on as thats the one that works the best for me, the diskcopy command seems to fail on everything, so I'm not sure if thats an issue with diskcopy itself. Files copy okay on 1.6.0 so thats fine.
Setpatch is a standard Commodore thing thats on every Workbench disk since 2.04, V37 is even up on aminet http://aminet.net/search?query=setpatch have a look on any Workbench disk after 2.04 and you'll find it in C:
The images I'm using are the ones from Cloantos Amiga Forever so I'd rather not be mailing those around, hope you understand.
If theres anything else you want me to test mate, just give me a shout.
Cheers
Mr.O
I've been through the firmwares you sent me and heres what I found..
1.6.0
Boot from WB3.1 floppy: Boots correctly, able to navigate around disk without read errors
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, everything worked fine.
Boot to WB3.9: Floppys are mounted correctly, able to navigate around them without read errors
tried copying files, everything worked fine
tried diskcopy df3: df0: (physical floppy to image) failed to verify track 0
1.6.2
Boot from WB3.1 floppy: Boots correctly, able to navigate around disk without read errors
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, threw 1 write error and produced later checksum errors on reading and deleting file.
Boot to WB3.9: Floppys are mounted correctly, able to navigate around them without read errors
Formatted an existing .hfe file successfully
tried diskcopy df3: df1: (physical floppy to image) failed to verify track 0
tried copying files, threw lots of write errors but was able to delete the file.
Reads everything I've tried without errors.
1.6.3
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.4
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.5
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
1.6.6
Boot from WB3.1 floppy: Serious problems, floppys don't mount, continually trying to read FAT table
Boot to WB3.9: Mounting problems continue, unusable.
As it stands I've left 1.6.0 on as thats the one that works the best for me, the diskcopy command seems to fail on everything, so I'm not sure if thats an issue with diskcopy itself. Files copy okay on 1.6.0 so thats fine.
Setpatch is a standard Commodore thing thats on every Workbench disk since 2.04, V37 is even up on aminet http://aminet.net/search?query=setpatch have a look on any Workbench disk after 2.04 and you'll find it in C:
The images I'm using are the ones from Cloantos Amiga Forever so I'd rather not be mailing those around, hope you understand.
If theres anything else you want me to test mate, just give me a shout.
Cheers
Mr.O
Re: Having a problem with a new rev F model
Yes please check your email box, a new firmware to test is available.Mr.Oakley wrote:Hi Jeff,
If theres anything else you want me to test mate, just give me a shout.
Cheers
Mr.O
Re: Having a problem with a new rev F model
Hi Jeff,Jeff wrote:Yes please check your email box, a new firmware to test is available.Mr.Oakley wrote:Hi Jeff,
If theres anything else you want me to test mate, just give me a shout.
Cheers
Mr.O
Just tried the new firmware, sorry to report I'm still getting the same problems as before.
I've flashed the drive back to 1.6.0 and it works fine.
Cheers
Mr.O
Re: Having a problem with a new rev F model
I have a similar setup, and the same problem
have the SD device for a week now, amazing piece of tech
Hope this bug gets worked out. If you guys need help let me know
System:
A4000D
- Cyberstorm 060
- Elbox zorro A4000DI
- a pci network card
- Ide to flash card holding a 4gb thingy
- SD Rev F
- fresh cd drive
- Indivision AGA 4000D
have the SD device for a week now, amazing piece of tech
Hope this bug gets worked out. If you guys need help let me know
System:
A4000D
- Cyberstorm 060
- Elbox zorro A4000DI
- a pci network card
- Ide to flash card holding a 4gb thingy
- SD Rev F
- fresh cd drive
- Indivision AGA 4000D
Re: Having a problem with a new rev F model
Ok another firmware sent to both of you.
Re: Having a problem with a new rev F model
Hi Jeff,Jeff wrote:Ok another firmware sent to both of you.
This is looking better, I've just managed to boot from a WB3.1 floppy and everything looks okay for reading from the disk.
Going to carry on testing
Cheers
Mr.O
Edit: Right, a bit more testing. Writing to disks causes checksum errors and renders the formatted floppy image unusable.
Tried booting into WB3.9 (from HD) and I'm back to the same errors as before, DF0: shows up as uninitialised and DF1: doesn't appear at all (should just have an empty floppy image in it.
Re: Having a problem with a new rev F model
i Run OS 3.9
Disks stil show up as uninitialized
Thay wil boot on there own
Disks stil show up as uninitialized
Thay wil boot on there own
Re: Having a problem with a new rev F model
Hi Dr.Dude,Dr. Dude wrote:i Run OS 3.9
Disks stil show up as uninitialized
Thay wil boot on there own
Sounds like we have a very similar setup and unfortunatly getting the same problems.
If you need to get up and running with the floppy emulator its worth asking Jeff to send you the 1.6.0 firmware, that seems to work the best so far.
Cheers Mr.O
Re: Having a problem with a new rev F model
Can you try to read some images with the patch loaded without writing to them for the moment ?Mr.Oakley wrote:Hi Jeff,Jeff wrote:Ok another firmware sent to both of you.
This is looking better, I've just managed to boot from a WB3.1 floppy and everything looks okay for reading from the disk.
Going to carry on testing
Cheers
Mr.O
Edit: Right, a bit more testing. Writing to disks causes checksum errors and renders the formatted floppy image unusable.
Tried booting into WB3.9 (from HD) and I'm back to the same errors as before, DF0: shows up as uninitialised and DF1: doesn't appear at all (should just have an empty floppy image in it.
Also : Try to remove the Drive B jumper.