would it be better to go down the CF route do you think?
I wouldn't abandon the sd interface yet. One thing you might try is connecting it to the PC using the IDE interface if that's not what you already did?
or this there a better way to copy files than using fuse?
hey, if it works it works, it works ;)
Presumably you can get all the files you want onto a 16-bit hdf with 3e/strowsaw then copy all the files to your 8-bit image with an emulator. Not ideal, but it's a workaround if 3e refuses to work with 8-bit files.
the other odd thing is that I can only create one 16 meg partition, but the sd card is 64 meg so i though i'd at lease be able to have 2 partitions on the drive and use 32 meg of the sd card?
the other odd thing is that I can only create one 16 meg partition, but the sd card is 64 meg so i though i'd at lease be able to have 2 partitions on the drive and use 32 meg of the sd card?
according to that image the +3e can see
473 cylinders * 8 heads * 32 sectors per track * 256 bytes = ~29.6 MB
you should be able to fit a 13MB partition in there
Presumably you can get all the files you want onto a 16-bit hdf with 3e/strowsaw then copy all the files to your 8-bit image with an emulator. Not ideal, but it's a workaround if 3e refuses to work with 8-bit files.
I use StrowSaw to edit 8-bit image files all the time. It works fine.
the other odd thing is that I can only create one 16 meg partition, but the sd card is 64 meg so i though i'd at lease be able to have 2 partitions on the drive and use 32 meg of the sd card?
I would check all the connections on the interface. I had a similar issue back ago; it turned out being a wrongly connected address line. if your interface uses lines A8, A12 and A13 you need to use the "sm8" rom variant. In the other hand if your interface uses lines A2, A6 and A7 you need to use the "pe8" rom variant.
Also I would try using something else than a SD card (just to see if the problem persist).
I use StrowSaw to edit 8-bit image files all the time. It works fine.
I would check all the connections on the interface. I had a similar issue back ago; it turned out being a wrongly connected address line. if your interface uses lines A8, A12 and A13 you need to use the "sm8" rom variant. In the other hand if your interface uses lines A2, A6 and A7 you need to use the "pe8" rom variant.
Also I would try using something else than a SD card (just to see if the problem persist).
Im using this scheme:
I've checked it over, and I cant see any mistake or loose wire, although it was a fiddly project to do on strip board, and the result is a tangle of wires.
although my interface has allowed me to create a HD, and read and write files successfully. I wonder if my problem is with a slightly dry of loose connection or its the sd card reader.
I don't have the equipment to test with a cf card, so that means a purchase. any recommendations for readers and cards?
The interface must be working fine based on what you've already done.
I would say the concerns are
1) how you are getting the image off and on the card causing possible issues
2) the IDE-SD interface not liking things
As BCH says, one easy test would be to try an IDE drive if you have one.
Did you try making another image and comparing that with what you wrote?
I'm very puzzled by the fact you can't create another partition. Is this since you wrote the image back to the card, or could you only fit one 16 meg partition on the disk from a fresh partition table?
EDIT: Aha, I see you only have four partition table entries, and the free space partition is broken
Ok, thats the one I use too. Should be fine on a strip board; just make sure you are using the "sm8" rom variant.
Maybe you have an old IDE hard drive around to do a quick test? That would do fine.
I got the rom from Gary L. for that specific interface, so I am assuming it's correct. Sadly I don't have an old hd, I thew it out a few years ago!! :-x
You can fix your image by opening it in a hex editor and replacing the start of the partition table with the following. That will give you more partition entries and repair the partition table.
You can fix your image by opening it in a hex editor and replacing the start of the partition table with the following. That will give you more partition entries and repair the partition table.
but i can map the the games drive. Also not able to load any game now. I was getting to a loading screen before the crash, but now it crashes dealing with the basic loader - it think.
I was wondering, if the current XT-IDE implementation could be ported to the +3? The latest revision does the 16/8 bit interfacing in a single CPLD instead of few logic chips. That way the full capacity of a mass storage was in use.
Also, would it be possible to create a terminal program that would enable to transfer files directly from PC to a Spectrum IDE partition via a serial cable?
but i can map the the games drive. Also not able to load any game now. I was getting to a loading screen before the crash, but now it crashes dealing with the basic loader - it think.
Once again, it's lost/corrupted the free space partition entry, presumably because it crashed before writing it.
Well it'd certainly be a known good configuration then.
The errors you're having are very odd though, since it clearly works. You can create a partition and create and delete files etc.
I would wipe the card and start again, forgetting imaging and whatnot and just try creating and deleting partitions of different sizes and see whether the issue occurs again. This would rule out any problems caused by drive imaging issues.
I was wondering, if the current XT-IDE implementation could be ported to the +3? The latest revision does the 16/8 bit interfacing in a single CPLD instead of few logic chips. That way the full capacity of a mass storage was in use.
There are plenty of options already for 16 bit ide interfaces. Most are a little expensive (divide) because they have ROM and RAM that are extraneous when using with a +3e. There's no reason at all that you couldn't build a 16-bit IDE interface for the +3e using a CPLD instead of discrete logic. The reason it hasn't been done is because no-one has got around to it...
Zetr0 has a designer poised to develop an internal 16-bit IDE/CF and software paged flash ROM replacement board for him... It is just waiting for a round tuit to be located ;)
Of course if you're using an IDE-CF adapter with a simple 8-bit interface it is possible to use the whole memory card, but that would require changes to the ROM ;)
Of course if you're using an IDE-CF adapter with a simple 8-bit interface it is possible to use the whole memory card, but that would require changes to the ROM ;)
Hmm? that was mainly another gentle dig at Zetr0 for when he next looks at this thread. ;)
He kept insisting that you need to use CF cards in a different mode with a different interface wiring, while I'm adamant that you don't but I don't have an IDE-CF adapter to test with so never got anywhere implementing it.
Then Zetr0 threatened to send me one so I would have to finish patching my driver to fully use CF cards :)
Hmm? that was mainly another gentle dig at Zetr0 for when he next looks at this thread. ;)
He kept insisting that you need to use CF cards in a different mode with a different interface wiring, while I'm adamant that you don't but I don't have an IDE-CF adapter to test with so never got anywhere implementing it.
Then Zetr0 threatened to send me one so I would have to finish patching my driver to fully use CF cards :)
ah, I see.
I know I could have made a CF interface that used the full card, but it would be good if you could do that with the interface I already have.
I believe the difference is between running the CF card in PATA IDE HDD mode vs. CF mode...
But even if we want to continue using PATA IDE HDD mode, to upgrade to a 16 bit transfer it only requires a 8 bit latch and two 8 bit tri-state non-inverting buffer chips to add the extra 8 data bits plus a little bit of glue logic (so maybe four or five 74LSxxx or 74HCTxxx chips).
! Standby alert !
“There are four lights!”
Step up to red alert. Sir, are you absolutely sure? It does mean changing the bulb!
Looking forward to summer in Somerset later in the year :)
I believe the difference is between running the CF card in PATA IDE HDD mode vs. CF mode...
CF cards can be set to 8-bit wide data transfers in True IDE mode the same as XT hard drives (pre-ATA), so with suitable firmware you should be able to use the whole card using a regular simple 8-bit interface and off the shelf CF-IDE adapter ;)
I suppose I'd better get on and produce a version of my spectranet driver as a working proof of concept hadn't I hehe :)
But even if we want to continue using PATA IDE HDD mode, to upgrade to a 16 bit transfer it only requires a 8 bit latch and two 8 bit tri-state non-inverting buffer chips to add the extra 8 data bits plus a little bit of glue logic (so maybe four or five 74LSxxx or 74HCTxxx chips).
As I say, there are plenty of designs for 16-bit interfaces. That is essentially what the divide does. The logic is slightly clever in how it controls the state of the latches but it is only a few chips yes (or you could do the whole thing in a single CPLD as I say).
Garry has +3e ROM sets available for pretty much all the existing speccy IDE interfaces on the +3e page. I'm only adding hardware drivers to my vapourware hard disk driver project as and when I find people with actual hardware to test it against :)
Garry has +3e ROM sets available for pretty much all the existing speccy IDE interfaces on the +3e page. I'm only adding hardware drivers to my vapourware hard disk driver project as and when I find people with actual hardware to test it against :)
Comments
Ok well it looks like a valid version 1.0 HDF with half sectors. 3e is able to read it here... (I have version 0.5alpha).
What's slightly strange is that 3e is reporting progs as partition zero and the system partition as 1 which is patently wrong :/
It will list the files on the partition but not get, put, or delete a file...
it seems to run absolutely fine in fuse, but not work so well on my real spectrum.
but the interface i built seems to be working correctly, for example IDEspeed works and jetpac loads fine on real hardware.
Oh, hang on, that's a disk image you prepared on the PC and the problem is writing it back to the sd card? hmm
yes, I formatted the sd card on my 3e, then copied the image to pc, added a load of files and copied it back to the sd card.
once back on the 3e its a bit flaky and most the the games wont load.
would it be better to go down the CF route do you think?
or this there a better way to copy files than using fuse?
Have you tried writing the image to the card, then creating a new image from it and comparing the two to check they're identical?
I wouldn't abandon the sd interface yet. One thing you might try is connecting it to the PC using the IDE interface if that's not what you already did?
hey, if it works it works, it works ;)
Presumably you can get all the files you want onto a 16-bit hdf with 3e/strowsaw then copy all the files to your 8-bit image with an emulator. Not ideal, but it's a workaround if 3e refuses to work with 8-bit files.
according to that image the +3e can see
473 cylinders * 8 heads * 32 sectors per track * 256 bytes = ~29.6 MB
you should be able to fit a 13MB partition in there
says disk full when I try. I even tried a 1meg partition, but it still said drive full.
I use StrowSaw to edit 8-bit image files all the time. It works fine.
I would check all the connections on the interface. I had a similar issue back ago; it turned out being a wrongly connected address line. if your interface uses lines A8, A12 and A13 you need to use the "sm8" rom variant. In the other hand if your interface uses lines A2, A6 and A7 you need to use the "pe8" rom variant.
Also I would try using something else than a SD card (just to see if the problem persist).
Maybe it's only raw disks it can't manage half sectors on then. I can't remember, it's a long time since I've used it in anger. :)
Im using this scheme:
I've checked it over, and I cant see any mistake or loose wire, although it was a fiddly project to do on strip board, and the result is a tangle of wires.
although my interface has allowed me to create a HD, and read and write files successfully. I wonder if my problem is with a slightly dry of loose connection or its the sd card reader.
I don't have the equipment to test with a cf card, so that means a purchase. any recommendations for readers and cards?
Maybe you have an old IDE hard drive around to do a quick test? That would do fine.
I would say the concerns are
1) how you are getting the image off and on the card causing possible issues
2) the IDE-SD interface not liking things
As BCH says, one easy test would be to try an IDE drive if you have one.
Did you try making another image and comparing that with what you wrote?
I'm very puzzled by the fact you can't create another partition. Is this since you wrote the image back to the card, or could you only fit one 16 meg partition on the disk from a fresh partition table?
EDIT: Aha, I see you only have four partition table entries, and the free space partition is broken
I got the rom from Gary L. for that specific interface, so I am assuming it's correct. Sadly I don't have an old hd, I thew it out a few years ago!! :-x
giving it a go...
the real hardware not so good.
I tried to create a new partition called "games" which i think got a read fail error
i then tried again but it said the partition already exists. so i hit cat tab and got some garbage
https://drive.google.com/file/d/0B8AEAM9VFI-NNjRLeTQ3X0ZIanc/view?usp=sharing
so i hit reset and do the same again and i get this:
https://drive.google.com/file/d/0B8AEAM9VFI-NMWx6bm93dzJXY3M/view?usp=sharing
but i can map the the games drive. Also not able to load any game now. I was getting to a loading screen before the crash, but now it crashes dealing with the basic loader - it think.
very tempted to by a CF card and reader.
Also, would it be possible to create a terminal program that would enable to transfer files directly from PC to a Spectrum IDE partition via a serial cable?
Well it'd certainly be a known good configuration then.
The errors you're having are very odd though, since it clearly works. You can create a partition and create and delete files etc.
I would wipe the card and start again, forgetting imaging and whatnot and just try creating and deleting partitions of different sizes and see whether the issue occurs again. This would rule out any problems caused by drive imaging issues.
There are plenty of options already for 16 bit ide interfaces. Most are a little expensive (divide) because they have ROM and RAM that are extraneous when using with a +3e. There's no reason at all that you couldn't build a 16-bit IDE interface for the +3e using a CPLD instead of discrete logic. The reason it hasn't been done is because no-one has got around to it...
Zetr0 has a designer poised to develop an internal 16-bit IDE/CF and software paged flash ROM replacement board for him... It is just waiting for a round tuit to be located ;)
the irony is not lost on me :-o:-o:-o
Hmm? that was mainly another gentle dig at Zetr0 for when he next looks at this thread. ;)
He kept insisting that you need to use CF cards in a different mode with a different interface wiring, while I'm adamant that you don't but I don't have an IDE-CF adapter to test with so never got anywhere implementing it.
Then Zetr0 threatened to send me one so I would have to finish patching my driver to fully use CF cards :)
ah, I see.
I know I could have made a CF interface that used the full card, but it would be good if you could do that with the interface I already have.
But even if we want to continue using PATA IDE HDD mode, to upgrade to a 16 bit transfer it only requires a 8 bit latch and two 8 bit tri-state non-inverting buffer chips to add the extra 8 data bits plus a little bit of glue logic (so maybe four or five 74LSxxx or 74HCTxxx chips).
PATA IDE Interface
Mark
Repair Guides. Spanish Hardware site.
WoS - can't download? Info here...
former Meulie Spectrum Archive but no longer available :-(
Spectranet: the TNFS directory thread
! Standby alert !
“There are four lights!”
Step up to red alert. Sir, are you absolutely sure? It does mean changing the bulb!
Looking forward to summer in Somerset later in the year :)
I suppose I'd better get on and produce a version of my spectranet driver as a working proof of concept hadn't I hehe :)
As I say, there are plenty of designs for 16-bit interfaces. That is essentially what the divide does. The logic is slightly clever in how it controls the state of the latches but it is only a few chips yes (or you could do the whole thing in a single CPLD as I say).
Garry has +3e ROM sets available for pretty much all the existing speccy IDE interfaces on the +3e page. I'm only adding hardware drivers to my vapourware hard disk driver project as and when I find people with actual hardware to test it against :)
Like this ?
Less excuses, more code :p