What's your experience with the new SD-Interface?
(+) well made -> doesn't look like a homebrewn device
(+) standard shugart bus -> not only for CPCs
(+) very easy to use: 3 buttons up, down & select
(+) huge blue display
(-) DSK files aren't supported: You have to convert all files to "HFE" ones
(-) I've successfully uploaded files to the sd interface. Problem: No app can handle these hfe-files expected the hxc one.Problem fixed v1.3.9.0
(-) Several DSKs I've copied back to 3" are corrupted copy protection?
(-) although it's jumpered as drive B, I have to select drive A after bootingThanks to nurgle for clearing this point
Still waiting for mine, but it's a worthwhile thread... maybe, if it builds up a little, we should send the link to the creator...
Some converted .dsk files don´t work.
E.g.: Prehistorik 2 (Plus version)! :(
I hope this game will be supported soon.
Quote from: viddi on 20:59, 11 May 10
Some converted .dsk files don´t work.
E.g.: Prehistorik 2 (Plus version)! :(
I hope this game will be supported soon.
But you can transfer it now to 3" or also 3,5" should work, too:
http://cpcwiki.eu/forum/index.php/topic,736.0.html
I know and already did. ;)
(CPCDiskXP also supports its protection)
HFE support would be nice, though. :)
Well I also tried transfer with CPCDiskXP and the disk failed to load...
But let's go back to topic ;)
Quote from: CPCIak on 13:07, 11 May 10
(-) although it's jumpered as drive B, I have to select drive A after booting
For those who do not own one: The SD-Card HxC can emulate two floppy drives on the shugart bus. Therefore you can select "Drive A" and "Drive B" in the menu on the display to insert two different images. When used as an external drive on a CPC6128 you can of course only use one external drive, this means you only use the first drive on the HxC. This leeds to the situation that you have to load an image into "Drive A" on the HxC which is then of course recognized as |B on the CPC as |A is the internal drive.
This is of course a cosmetic issue and not a real problem. I have an ABBA switch in my CPC6128 which means I always insert images into "Drive A" in the HxC which then becomes |A or |B on my CPC depending on the position of the ABBA switch.
Quote from: CPCIak on 13:07, 11 May 10
(-) Several DSKs I've copied back to 3" are corrupted
I havnt had this error myself. But i did have a HFE being wrongly read because i shut the power off before "ejecting" the image. Seems to me its quite importent that you remember to eject and remount the floppies before turning off/on.
Another Con: the powerplug on the SD version is somehow not compatible fully with a normal pc power cable. So you either make a hole or file off the "tooth" so that the pc cable will able to lock on correct.
A new software version has just been released (v1.3.9.0)!
Now it's possible to convert hfe- into dsk-files :)
http://hxc2001.free.fr/floppy_drive_emulator/HxCFloppyEmulator_soft.zip (http://hxc2001.free.fr/floppy_drive_emulator/HxCFloppyEmulator_soft.zip)
Quote from: CPCIak on 07:19, 12 May 10
A new software version has just been released (v1.3.9.0)!
Now it's possible to convert hfe- into dsk-files :)
http://hxc2001.free.fr/floppy_drive_emulator/HxCFloppyEmulator_soft.zip (http://hxc2001.free.fr/floppy_drive_emulator/HxCFloppyEmulator_soft.zip)
Woohoo! Looks like praying to the old gods actually works.
Ahhh now you're talking :)
I think my unit is at the post office, got a notification today... did he send them out registered/signed-for?
Quote from: Gryzor on 18:57, 12 May 10
I think my unit is at the post office, got a notification today... did he send them out registered/signed-for?
Yes, you are right Gryzor!
Quote from: Gryzor on 18:57, 12 May 10
Ahhh now you're talking :)
I think my unit is at the post office, got a notification today... did he send them out registered/signed-for?
Indeed both the USB and SD one came with recorded mail.
Wiki updated a bit:
http://www.cpcwiki.eu/index.php/Guide_for_HxC_SD_Version
Found another Con:
- unlike with a real drive, you cant format the disc. Like if you have a Data disc then you cant copy a System disc on top of it. Or you cant copy a 42 track disc on a 40 track image.
So, is it worth getting one of these?
I'm considering one for my CPC6128
Also, will it work with a CPC464? do I need the FD-1 (or is it the DD-1, can't remember) interface for use with a CPC464?
Quote from: woody.cool on 22:33, 18 May 10
Also, will it work with a CPC464? do I need the FD-1 (or is it the DD-1, can't remember) interface for use with a CPC464?
Logically yes.
You need the controller.
It's easy to modify it to get power from 464. (Short C115 on it's pcb, that's all)
Quote from: Devilmarkus on 22:33, 18 May 10
Logically yes.
You need the controller.
It's easy to modify it to get power from 464. (Short C115 on it's pcb, that's all)
Nice one!
Considering a purchase now.
Quote from: woody.cool on 22:38, 18 May 10
Nice one!
Considering a purchase now.
But remember:
When you modify it's power input, and you want to use it later with a 3" drive, you need to undo this change.
Quote from: Devilmarkus on 22:40, 18 May 10
But remember:
When you modify it's power input, and you want to use it later with a 3" drive, you need to undo this change.
It's mostly for use with my 6128 tbh, but maybe the odd time on the 464.
Has anyone tried out the new firmware v.1.1.1.0?
How do you know which version you have? And where did you see 1.1.1.0? And what's new? And how do you install it? :D
Well, I got my unit on Friday... and now I can't find my 6128s!!!!! Ahhhhh darn...
I also bought a new SD card and upon starting the program I found that big con about the size of the generated files... You see, I bought a 2GB SD card thinking it'll be plenty for the CPC collection, but of course... Oh well.
The actual firmware is shown when you switch on the interface.
News & updates from the author can be found here: http://hxc2001.free.fr/floppy_drive_emulator/index.html#intro (http://hxc2001.free.fr/floppy_drive_emulator/index.html#intro)
In order to update the firmware you've got to copy the *upd and *cfg file to a fresh formated SDCard
Thanks... his web pages are all over the place!
Upgrading the firmware is also expained in the Wiki:
http://www.cpcwiki.eu/index.php/Guide_for_HxC_SD_Version
Anyone spots new functionality with the new firmware, please speak up ;)
Yeah, silly me, I read the article later...
But the changelog doesn't have any major new functionality, I doubt you'll notice anything unless you have an Amiga?
Look at this good french modding :
http://img199.imageshack.us/img199/9587/photoqoc.jpg (http://img199.imageshack.us/img199/9587/photoqoc.jpg)
From the french forum :
http://cpcrulez.fr/forum/viewtopic.php?f=5&t=100&start=120 (http://cpcrulez.fr/forum/viewtopic.php?f=5&t=100&start=120)
This is just great.... wish I could do it myself!
The cut-outs are a bit rough (around the buttons) and the disc-drive looks like it's a fake PC 3.5 bay-cover, but a good idea.
Bryce.
May one of you friendly guys here can test the SD Card Floppy emulator with FutureOS? Would be great to know if it can read and especially write files. Please help me with this, I can't test it by myself.
Why wouldn't it? I mean, it's supposed to appear as a real drive...
Just quick stupid question: any experiences with 6128+ and HxC SD version?
(Reason why i'am asking: Just upgraded my PC and new one does not have floppy disk controller anymore ??? :o )
Hi jsa, you don't need a floppy controller in your pc in order to work with the SD interface!
The floppy cable is connected to the cpc - not to the pc.
All you need is a cardreader
Please have a look at the user manual
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_User_Manual.pdf
Quote from: TFM on 22:39, 02 June 10
May one of you friendly guys here can test the SD Card Floppy emulator with FutureOS? Would be great to know if it can read and especially write files. Please help me with this, I can't test it by myself.
A very good question indeed. I dont have the FutureOS roms in my cpc. But the software seems to correctly convert the 800kb large DSK files to HFE and back to DSK again too.
Quote from: jsa on 22:22, 04 June 10
Just quick stupid question: any experiences with 6128+ and HxC SD version?
(Reason why i'am asking: Just upgraded my PC and new one does not have floppy disk controller anymore ??? :o )
I dont have a 6128+ to test it with, but since they are selling a 6128+ cable at:
http://myworld.ebay.co.uk/urban-retro/
.. it probably works ok ;)
Been using the new firmware 1.1.1.0 for some days now and it works ok. Didnt notice anything different from the previous one tho. So only limit is still that you cant reformat floppies from one format to another.
I have tested the SD interface on a CPC6128 with the Orion Prime french image and it works beatifully well.
I also managed to save the game and load it again.
Nice piece of hardware indeed.
13/06/2010: Firmware SD HxCFloppyEmulator v1.1.2.3
- Atari ST/STE/Falcon :"Write protect" disk change emulation implemented (disk change detection is now working correctly).
- Direct Access mode : Density select signal set in the right state. (Atari ST computer with HD able FDC)
- HFE file format : new parameter : "Write allowed" byte.
- Some code optimizations (speed & size).
Does this mean formatting (data <-> system) is possible now?
Quote from: CPCIak on 07:07, 14 June 10
Does this mean formatting (data <-> system) is possible now?
Sadly, i noticed no difference using the new firmware and software. Like: Still cant copy a simple data disc on top of a cpm one. Note this is ONLY when copying to the SD HxC .. because it works brilliantly when you copy from the SD HxC to a real drive. Also there is no troubles copying files back and forth. So its only when you deside to make backups of your real discs that you need to make sure that the destination HFE is the same format/no. tracks that you copy from.
That's a really minor niggle, ain't it?
Quote from: Gryzor on 13:44, 15 June 10
That's a really minor niggle, ain't it?
True, true.
Most people would probably not even notice this as "primary" use of this device is probably to copy discs PC -> CPC (aka play games or similar). And CPC -> PC also works as long as the format is the same (or you copy files). And its easy to make as many empty data or system or large track disc as you want using a emulator, managedsk or similar and put them on the SD card like data01.hfe, data02.hfe, data03.hfe, system01.hfe, system02.hfe ...
So making backups of you old data/system discs is no troubles even tho a bit incovenient having to check format first.
Workaround: Use Xexor or similar tool to archive your disc as a single compressed file. Like: "archive floppy01" will write a floppy01.arc file on the destination floppy. Once the hfe with the file on has been extracted to dsk, just "extract floppy01" will write the floppy back inside a emulator on pc. This works with most normal discs independant on format or size. Still, you wont be able to make backups of most of your protected games.
Again, the Hxc SD is a really cool tool and it works really great, so dont let my rantings stop anyone from getting one (its 10 trillion times easier than ye ol' cable transfers). 3 years ago I would have sold my own mother to get one of these ;D
I received my SD HxC a few weeks ago now; I got it for my Atari STE and Falcon 030 machines, but seeing as it also supported other computers from my youth such as the Amstrad CPC6128 and Sinclair ZX Spectrum +3 128K, I ended up buying a CPC6128 and +3 128K along with lots of extra hardware for them. I've not had chance to use it yet though as I am trying to find decent SDHC cards that are not a rip off, although I missed out on a Sandisk Ultra 32GB card on Ebay that sold for £41. At first I planned on buying a few 4GB cards but I now think a single 32GB would be better, with each computer in a seperate folder etc. It's good to see that the developer listens to his customers and then improves the firmware; I suggested that he made image selection easier by implementing an on-screen method, and a week or two later this was in the next firmware. Prior to this you could only select images via the hardware buttons on the board.
By the way in my youth I actually had the CPC464 in 1987 and I bought approx 500 games for that. I also had a ZX Spectrum 48K (rubber keys) in 1983 which was replaced numerous times under warranty, before in 1985 I ended up with a +48K as they had no more rubber key models.
Anyway once I have bought a good SDHC card for it, I will report back here on how well it works with my CPC6128 (and Spectrum +3 128K if anyone is interested).
A 030... ooooooh I want one...
Hehehe I have two Falcon 030 at present, both with 68882 FPU and one with 14MB and lots of Steinberg and SoundPool hardware. Actually a little potted history of me now... Once the 1980s had ended and the 1990s began, my interest in being a musician took over from my gaming obsession on my CPC464 and Speccy 48K. In 1994 I bought a Atari STE + monitor from my friend as he needed the funds towards his dream Land Rover MkII. The STE was ONLY used for making music with Cubase and Band-in-a-Box and then one day in December 1999, I decided to plug the STE into my portable 14" colour TV and try out a PD game I had downloaded at a friends place. It was a fabulous pinball game called Starball and from that moment I was hooked on home micros again! Shortly after though my uncle gave me a PC and I got my own internet connection and my interest in 1980s micros was gone. However I still occasionally had a peek at emulation stuff but never really did anything, until in September 2008 I saw an Atari STE auction that seemed too good to pass up, so I bought it. Since then I have bought so much stuff I am struggling to find room in the house for it all, and I am supposed to be getting the house ready to move!
I now have:
Amstrad CPC6128 + 3.5" Ext. Floppy + SD HxC Floppy Interface
Atari STE x3 + everything you can think of IDE, SCSI, scanner, video capture, 16-bit audio and so on...the list is almost endless!
Atari Falcon 030 x2 + large selection of hardware
Sinclair ZX Spectrum 48K (rubber Series 2)
Sinclair ZX81
Sinclair ZX Spectrum +3 128K
Sinclair ZX Spectrum+ 128K (black heatsink model) died a month after buying by using wrong PSU polarity
Commodore 64 (breadbin) died in summer heat the other day after only two weeks of ownership
Psion Series 3
Psion Series 3mx + 4MB RAM card + other stuff
Most of the stuff that takes up lots of room are all the addons, cables, adapters, PSU, mice, floppy disks, CD/DVD ROMs etc.
Soooo mate, how about donating one of those Falcons there to the wiki? I'll even put a virtual shrine up in your honor - heck, I'll give you the admin password!
I see we had similar tastes... though I've lost my Psion and also have some Amigas/Sam Coupe's/Enterprise64 lying around...
Oooh I dunno, your Sam Coupé and Enterprise64 are far more rare than a mere Falcon 030 ;D However owning a Falcon 030 is a spiritual experience direct from the retro gods themselves :angel: ;) Actually today I may finish the job of housing a VERY noisy SCSI 10000rpm drive in a Scythe Quiet Drive enclosure, into my PC tower so that I can begin using Cubase Audio for my Falcon 030 with my studio setup. One way or another I have used Cubase since 1990 and the Atari versions are perfect, whereas all the PC versions are bloatware of the worst order; far too complex and over specified.....I just wanna sequence some music for gods sake! ::) I've never done any sequencing on an CPC or Speccy though, and the Speccy I have now has a MIDI OUT port albeit with a telephone style socket and limited polyphony/channels.
QuoteCommodore 64 (breadbin) died in summer heat the other day after only two weeks of ownership
He was probably killed by the numùerous speccies, lead by the Amstrad CPC (Speccy being an amstrad property...lol) : rebellion in Geekland...
Computers can be cruel... ???
You said you used Qbase...but did you achieve some YM tunes (with soundtrakers per exemple) ? as you lknow, those can be used on Speccies128 and amstrad (AY)... If so I hope you will upload them on the many AY/YM tunes databases...
YM tunes? Nope I have never made any music with them as I am a musician in the full sense, i.e. learning instruments, arrangements and theory and studio/stage craft etc. Tracker style stuff can be great and I respect what people do with it sometimes, but I would struggle to write music that relied upon repetitive patterns and simplistic styles. However in my first tentative steps into learning music between 1985 and 1992, a lot of what I did would probably have been easy to convert into tracker style tunes.
My first computer-music was coded in BASIC on the CPC. :)
I looked up the frequencies in the back of the manuel, and wrote them down on a piece of paper on top of my cool drawing of a keyboard or piano. And then I used DATA lines to create the music. Very time consuming work...hehe.
I also had a Psion MC218. It broke. Got another one a few years later, but don't use it anymore now that phones can do a lot of the stuff. I tried the HP Jornada 720 as a replacement for my Psion, but that just didn't work out. Maybe the www.openpandora.org would work out as a decent replacement....
The Psion Series 5mx was an excellent machine. My uncle has a few of them and I still have a Psion Series 3 and Psion Series 3mx which are also superb.
You're spot-on. For some reason I've been longing for a 030, though I never had one, nor will it offer me much my STFM/STe/MegaST/MegaSTe won't offer me. Darn I want one!
Not in a PC case though, it makes no sense for me...
But we're waaay off-topic!
Quote from: Shredder11 on 12:40, 09 July 10
Oooh I dunno, your Sam Coupé and Enterprise64 are far more rare than a mere Falcon 030 ;D However owning a Falcon 030 is a spiritual experience direct from the retro gods themselves :angel: ;) Actually today I may finish the job of housing a VERY noisy SCSI 10000rpm drive in a Scythe Quiet Drive enclosure, into my PC tower so that I can begin using Cubase Audio for my Falcon 030 with my studio setup. One way or another I have used Cubase since 1990 and the Atari versions are perfect, whereas all the PC versions are bloatware of the worst order; far too complex and over specified.....I just wanna sequence some music for gods sake! ::) I've never done any sequencing on an CPC or Speccy though, and the Speccy I have now has a MIDI OUT port albeit with a telephone style socket and limited polyphony/channels.
No no nooooo, my Falcon 030 is in it's original case / form factor; it is only the external SCSI drive that I am housing in a PC tower as I had a bay spare, and near enough the Falcon case. However in the future I may decide to finally use my Eiffel PS/2 keyboard and mouse interface, and I do not want to butcher my lovely Falcon case to fit it so a tower may come into play then. For now though my two Falcon 030 are in their Atari cases.
Right back on topic! ;D
Hi,
I have just finished the port of the HxC Floppy image tool manager to CPC.
(http://hxc2001.free.fr/vrac/SDHXCFEM_CPC.jpg)
I need some feedbacks, and since it seems there some hxc floppy emu users here i post the link to this tool here :
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip (http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip)
NOTE : you need to update your firmware version before use it, and the HxC Floppy must be the first disk drive.
Jeff / HxC2001
Hello mate!
So glad to see you here, and thanks for the tool...
Since I'm a sad, sad individual and still haven't found the time to even test my emu, could you describe what this tool does? Is it a replacement for the hardware interface?
Quote from: Gryzor on 08:01, 15 July 10
Hello mate!
So glad to see you here, and thanks for the tool...
Since I'm a sad, sad individual and still haven't found the time to even test my emu, could you describe what this tool does? Is it a replacement for the hardware interface?
This a tool that allow you to choose the floppy images directly with the CPC.
Here a demo of this tool on Atari ST: http://www.youtube.com/watch?v=8O74GgYcA3w
Hello,
i checked and tried the new tool, it's working fine. Thank you so much for that !!!
Kindly regards
Tom
[youtube=8O74GgYcA3w]ST vid[/youtube]
So many systems, so little time... :(
New version available !:
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip
Quote from: Jeff_HxC2001 on 20:32, 17 July 10
New version available !:
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip (http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip)
Hi Jeff,
I've tried this new version... but I keep getting the error message after the prog mounts the SD card:
FAT_FS: Error could not load FAT details (-2)!
I'm using a freshly formatted FAT32 SD card (tested with 128MB and 2GB capacity cards, quick format and full format on WindowsXP) and using the supplied autoboot.hfe and hxcsdfe.cfg files as the first two files on the card on my CPC6128. Reformatting using the Panasonic SD Formatter only creates a FAT format SD card, and then HxC FE complains that it can't find the CFG file on the card - reformatting with WinXP clears this..
any tips to get it working?
Pleasy tell me :
What is your computer ?
Did you have some extensions connected to it ?
How is connected the HxC Floppy Emulator (port / drive ID ...)
What is your firmware version ?
Can I use the new manager with SD interface as Drive B?
Quote from: CPCIak on 14:00, 18 July 10
Can I use the new manager with SD interface as Drive B?
Now you can ;) :
v1.3a:
support drive b.
http://hxc2001.free.fr/floppy_drive_emu ... anager.zip (http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Manager.zip)
A video demo of this tool on CPC :
http://www.youtube.com/watch?v=bnyC5te6Mn0
Quote from: Jeff_HxC2001 on 13:35, 18 July 10
Pleasy tell me :
What is your computer ?
Did you have some extensions connected to it ?
How is connected the HxC Floppy Emulator (port / drive ID ...)
What is your firmware version ?
Hi Jeff
using the HxC SD FE on a CPC6128 - without any extension hardware
It's connected via the external floppy connector, with the jumper block setting it as the A drive (I'm using a ABBA type mod to switch it to A, and the internal 3" as the B drive)
firmware version is v1.1.2.4 (updated from previous version 1.1.2.3)
please note: there's no problem using it as a floppy/DSK emulator to load DSK games via the buttons and LCD screen with the CFG file I generated for version 1.1.2.3
hope this helps :)
Hi,
I have downloaded the latest version of the "Floppy Emulator Manager" (v1.3a), and it is a big step forward in using the SD card. It became much easier to select an image, and I was able to use a directory structure on my cards. Excellent program :D ! ! !
Yesterday I spent a few hours playing around with it, and I discovered a few "odd" things about it. ???
1.) About 10-20% of the times I did restart my computer and ran the HXC software, it wasn't able to find the interface. The error message I get on my CPC6128 is as following :
- "Bad signature - HXC floppy emulator not found! (0)"
The LED display says :
- "Direct access : LBA 00000000"
I have tried several times to try to find a pattern and a reason for this to happen, so far without any luck ! ! !
2.) When it works (80-90% of the time) I'm able to use the software. Finding an image I want to use, I mounts it on drive B, and saves and restarts my CPC. Choosing drive B I only finds the HXC image. No other images is found when pushing the <Left> or <Right> button. Running HXC software, and browsing through the different slots, no software is found in any of the slots. OK trying again, finding a few images, mounting them on drive B, saving and restarting. Same procedure, still no images on drive B besides the HXC software.
After several more attempts, with the same result, I did a small discovery. I had by accident chosen the same image on BOTH drive A and B. After saving and restarting, the image turned up on drive B. Guess if I was surprised ???
Doing a few more tests based on my new learned knowledge, I discovered that I had to mount the software on DRIVE A to be able to use it from DRIVE B. This sounds a bit ODD to me, and perhaps it is an bug in the software ? ? ?
Hopefully my experiences can be of any help to You Jeff.
Yours
Terje Grind
NORWAY
PS My setup is as following :
- Amstrad CPC6128 (no additional hardware)
- Disc drive lead, and SD power cable from Urban-retro
- HxC SD-Interface with version 1.1.2.4
- Interface jumpers set as drive B
SD-card :
- 2GB SD SanDisk Ultra II Class 4
- Formatted as FAT32
- Files are copied to the blank card in the following order :
1.) (HXCFE_V1_1_2_4.UPD)
2.) (Hxcsdfe.cfg)
3.) (AUTOBOOT.hfe)
4.) A lot of HFE files
Im getting the same error as Terje (Bad signture) and the display says: "LBA:20004546".
Setup: 464 with DDI (DFO) and HxC (DF1). Normally no troubles with this setup.
Used all the latest files (firm 1.1.2.4, soft 1.3.11.0 and v1.3a).
Used soft 1.3.11.0 to turn off "bootselector" and saved it to SD card ( HXCSDFE ).
SD card: 512mb Lexar.
Running the software from B .. it loads up and the display says "direct access" but then quickly gets the error. Running the software from A and screen says "bad signature" but no "direct access" or "LBA" error at all (aka the board isnt reached .. but i guess its quite normal because there is no hcx on A drive).
Firmware update !! :
Version 1.1.3.0 :
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_firmware.zip (http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_firmware.zip)
This one should correct most issues reported here.
Thanks for yours feedback!
Just tried the new 1.1.3.0 firmware, and still getting a "Bad signature" on screen, but the error message on the hxc display has changed to "LBA: 0000000000".
(464+DDI+HxC).
Quote from: Cholo on 19:08, 25 July 10
Just tried the new 1.1.3.0 firmware, and still getting a "Bad signature" on screen, but the error message on the hxc display has changed to "LBA: 0000000000".
(464+DDI+HxC).
Probably a compatibility problem of the software with the 464.
What is the top mem address that a software can use on this computer ? (and with the DDI?).
Maybe this is helpful:
http://cpcwiki.eu/index.php/File:Mg_page26.jpg (http://cpcwiki.eu/index.php/File:Mg_page26.jpg)
http://cpcwiki.eu/index.php/Amstrad_Micro_Guide (http://cpcwiki.eu/index.php/Amstrad_Whole_Memory_Guide)
Quote from: Jeff_HxC2001 on 07:36, 26 July 10
Probably a compatibility problem of the software with the 464.
What is the top mem address that a software can use on this computer ? (and with the DDI?).
Indeed it could be a memory problem, but as the 6128 has even less space than the 464+DDI (that is why some old 464 programs wont run on a 6128 as they are too large), i think the must be the interface that does something different than a 6128. But its just a guess. The software seem to be loading and running alright so that might suggest that there is no memory troubles either. Also on every attempt there do seem to be access to the interface of some kind, so something is definately comunicating. Still, the 464 originally didnt support floppies and im guessing there is quite a difference in how the DDI accesses the drive than the 6128 does it.
I cannot seem to run the 'Floppy Emulator Manager' software, it displays 'Loading' but never gets any further.
What am I doing wrong?
I have formatted a SD Card, copied the Upgrade and matching CFG file of the latest version v1.1.3.0 and this upgraded the firmware successfully.
I have the ID1 set to the top 2 pins (as an external drive B). If I copy a .hfe file to the SDCard, I can select 'Drive B', select the file and upon typing '|b:cat', I can see the DSK image and can run the software.
I wanted to use the new 'Manager' software, so I formatted the SDCard, copied the autoboot and CFG file to the card and a single .hfe file. The card boots up, I can type '|b' and 'run "hxc"', but I am then only shown the 'Loading' wording and the program never finishes loading.
I am using a CPC 6128 with no other attachments.
(I tried replacing the CFG file with the latest UPD version, but that fails also).
Any assistance greatly appreciated!
thanks
Quote from: ynot.zer0 on 19:01, 28 July 10
I cannot seem to run the 'Floppy Emulator Manager' software, it displays 'Loading' but never gets any further.
What am I doing wrong?
[...]
I have the ID1 set to the top 2 pins (as an external drive B). If I copy a .hfe file to the SDCard, I can select 'Drive B', select the file and upon typing '|b:cat', I can see the DSK image and can run the software.
Use the lower pins not the top. If you emulate only one disk drive there are not point to use the second drive slot of the emulator! The autoboot.hfe must be in the "drive A" slot of the emulator (but this drive slot can be mapped to the disk drive a or b of the CPC).
Hi,
in the end I took a look at these 2 wiki articles:
http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5 (http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5)
http://www.cpcwiki.eu/index.php/HxC_SDCard_Internal (http://www.cpcwiki.eu/index.php/HxC_SDCard_Internal)
I noticed that in the first article, under 'The Cable' section it mentioned using an old PC floppy cable - I just happened to have one in my 'spare parts drawer'. So, I set about making the SDCard the internal disc drive. It is now the 'drive A' as I have the pins shorted on pin 11&12 (as shown in the picture http://pchan.250free.com/CableClose1.JPG (http://pchan.250free.com/CableClose1.JPG) )
When I now run "hxc", the software inits the SDCard properly and I can use the tool - excellent!!! great stuff...
I'm now about to convert all my software to .hfe format.
thanks
Great !
Note to all HxC Floppy Emulator users : if you like the product don't hesitate to spread the word about it ! ;D
Your support is important !
Finally had time to mess around with this ;D
Have to say that this is really good piece of HW to used with CPC's.
After doing some additional power adaptors for CPC6128+ actual emulator worked fine :)
Only problem was that at first SD card was formatted with FAT instead of FAT32. RTFM error so to say...
I tried the emulator with a Dragon64 and it worked flawlessly.
I'm pretty glad I bought it ;D
Quote from: Jeff_HxC2001 on 13:29, 30 July 10
Note to all HxC Floppy Emulator users : if you like the product don't hesitate to spread the word about it ! ;D
Your support is important !
We even go so far as to say you might take it to the next, i.e. mainstream-compatible "industrial" level: http://cpcwiki.eu/forum/index.php/topic,1106.msg11342.html#msg11342 :) - and (travelling far from my CPC) I haven't even personally had one yet...
Jeff: as far as Greece goes, you can try posting at retromaniax.gr . This is a retro forum with a big computing section, and people will love to hear from you, even in english (lots of devs do it).
Btw: any hope there will be a solution, some day, that won't need those huge converted image files?
Quote from: Gryzor on 06:53, 02 August 10
Btw: any hope there will be a solution, some day, that won't need those huge converted image files?
No way ! : i have already explained my point of view here :
http://eab.abime.net/showpost.php?p=685774&postcount=40
Quote from: Jeff
Quote from: Akira;685734Hi Jeff!
Thanks a lot about your work on HxC
I am still curious as to why different file formats cannot be supported and you need to convert. A little more in-depth explanation will clear people's doubts ;)
Mainly Because :
A low cost MCU have low memory, and are not very powerfull.
Example:
The HxC Floppy Emulator and The SDiskEmul uses a PIC18F4525 MCU.
its Specifications are :
-10Mips MCU @ 40 Mhz
-48kB of Flash.
And the most problematic thing:
-3900 byte of RAM
>Flash Size problem : This is very hard to implement all file format in the firmware (flash space problem).
The actual loaders of supported by the HxC Floppy Emulator (36 formats supported !) take 300KB of code.
>RAM Size problem: With less of 4Kb of RAM, hard to implement an gzip lib in the pic (ADZ format...) or directly managed complex format as IPF.
>Speed problem : In any case data must be converted to MFM/FM (all emulators does this) and for this you need time (and memory space). Making the conversion of an ADF file can be long. For example on SdiskEmul this take 20 seconds (and this is in ASM) ...
Additionally I think that the pre-conversion isn't a problem: In anycase you use a computer to copy image file to the SDCard. So conversion program or not, this doesn't change nothing for me. On the contrary this make the device more reliable (final image file are verified – the mcu code implementation is simpler -> less potential bugs).
If the conversion program are well designed, this can be a powerful tool to managed floppies images. You can also create AmigaOS image file with some files present on the pc.
With the HxC Floppy Emulator software you can convert a complete tree of file images by a simple drag&drop.
Finally this conversion program make the hardware secondary (I think this important for the future...). I can change the MCU by another one, or an fpga without rewriting the whole thing.
So from the developer point of view the central point of the hxc floppy emulator is the conversion program, not the hardware.
This how I design the whole project, and this will not change in the future.
But I believe that MCUs will be powerful enough to directly digest the conversion tool latter.
Last words : We have sold hundred's of floppy emulators, and I have no bad return from users about the conversion program.
(I have probably forget some arguments here ;-) )
And with a 16GB sdcard i don't where is the problem ! ;)
Well mine arrived today (much quicker than I expected) and I have to say it's absolutely brilliant! ;D
Had a few teething troubles as it refused to see one of my old SD cards, but once I swapped that out it's all been plain sailing. My 6128+ has a whole new lease of life all over again. I'd highly recommend everyone get one of these.
Hey Jeff,
Thanks for the explanation. Well, just for discussion's sake, loaders could reside on the CF itself, but this still wouldn't address the speed problem.
Hey, I just saw that a 16GB SD is only €29 in Greece!
Here's a question for jeff, will the floppy emulator work with a disk controller that does not have a data separator, I have a 464 plus and can get most of the parts needed to populate the disk controller section of the pcb, but I doubt that I could get a data separator, I want to install the hxc inside the case so the connections from it to the FDC will be short, but do you think it would work?
Soooo.... today I finally found my 6128. It was in a mislabeled box, dammit!!!
I upgraded the firmware, fiddled around for several minutes before realising I hadn't connected the floppy drive (geez...) and couldn't get the machine to read drive B, then tried to load Gryzor... only to fail, because it apparently wants to reside on Drive A (anyone can confirm this?). Damn. I'm tired, off to bed with my book for now.
One question though - what are these slots supposed to be???
Oh - and another question: how do you run multi-face or multi-disk games? I was thinking Orion Prime... or is it, indeed, the slots thing? Do you import different dsk's in different slots and then reboot?
Cheers
Gryzor
Quote from: Gryzor on 21:41, 04 August 10
Soooo.... today I finally found my 6128. It was in a mislabeled box, dammit!!!
I upgraded the firmware, fiddled around for several minutes before realising I hadn't connected the floppy drive (geez...) and couldn't get the machine to read drive B, then tried to load Gryzor... only to fail, because it apparently wants to reside on Drive A (anyone can confirm this?). Damn. I'm tired, off to bed with my book for now.
One question though - what are these slots supposed to be???
Oh - and another question: how do you run multi-face or multi-disk games? I was thinking Orion Prime... or is it, indeed, the slots thing? Do you import different dsk's in different slots and then reboot?
Cheers
Gryzor
Exactly. Insert in each slot a disk/face of a game.
During the game you have just to push the right button to change the disk. (right increment the slot number, left decrement, middle: select the manager disk).
On CPC 6128 you can for the external disk drive as A without open it : just connect pin 23 & 24 together of the floppy cable.
For more details : http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_User_Manual.pdf
Quote from: steve on 19:50, 04 August 10
Here's a question for jeff, will the floppy emulator work with a disk controller that does not have a data separator, I have a 464 plus and can get most of the parts needed to populate the disk controller section of the pcb, but I doubt that I could get a data separator, I want to install the hxc inside the case so the connections from it to the FDC will be short, but do you think it would work?
mhh no the FDC need a Clock to be able to get data. So the data separator is needed.
On some japanese machine the data separator is located in the disk drive, so to support them i have to design a small board to generate this clock.
For the moment this will not work.
Quote from: Gryzor on 19:42, 04 August 10
Hey Jeff,
Thanks for the explanation. Well, just for discussion's sake, loaders could reside on the CF itself, but this still wouldn't address the speed problem.
Hey, I just saw that a 16GB SD is only €29 in Greece!
Which speed problem ? The loading time of the manager ?
Hello Jeff! So nice to see you're following the thread :)
Yeah, I have the manual printed by me and I saw the twisting solution, I think I prefer to disable the internal drive altogether though.
On another note, can you provide some info on the display info? For instance, what's that "RA" indication flashing up there? And Sx? Is this supposed to be Slot #(it doesn't change on mine)?
Also, on the interface, there must be a misunderstanding somewhere... according to the UI, it keeps inserting images to "Drive A" though I have set it up to be Drive B.
Quote from: Jeff_HxC2001 on 07:52, 05 August 10
Which speed problem ? The loading time of the manager ?
The conversion and loading time. You said loaders take up a lot of space and (if I'm reading this correctly) this is why you have ended up with a common file format that, I guess, only needs one loader. So, as I said, you could keep the original files and load the loader from the SD each time - one loader for DSKs, one for ADFs, one for MSAs... but still, this would entail a delay while the board does the conversion - 20 secs, as you say.
Quote from: Gryzor on 07:52, 05 August 10
On another note, can you provide some info on the display info? For instance, what's that "RA" indication flashing up there? And Sx? Is this supposed to be Slot #(it doesn't change on mine)?
No the slot number isn't printed on the lcd :
RA: Read A
RB: Read B
SX: Side X
Quote from: Gryzor on 07:52, 05 August 10
Also, on the interface, there must be a misunderstanding somewhere... according to the UI, it keeps inserting images to "Drive A" though I have set it up to be Drive B.
No there are no error : Drive A & B in the emulator correspond to Drive A & B of the emulator !!!! After for the system this depend what setting you have : For example with the jumpers you can connect the "Drive B" (second drive) of the emulator as drive A for the host system. In fact i need to change the name "Drive A" / "Drive B" by something else.
Quote from: Gryzor on 07:55, 05 August 10
The conversion and loading time. You said loaders take up a lot of space and (if I'm reading this correctly) this is why you have ended up with a common file format that, I guess, only needs one loader. So, as I said, you could keep the original files and load the loader from the SD each time - one loader for DSKs, one for ADFs, one for MSAs... but still, this would entail a delay while the board does the conversion - 20 secs, as you say.
Yes this a good idea but this can't be done with this MCU : There are very few ram (<4KB) and the number of flash reprogramming is limited.
Thanks for the indications info.
On the UI: I'm still a bit confused after your answer. Maybe I've missed something vital - the emulator can actually emulate two drives? And, I thought the jumpers control the emu's single drive letter, so that you can set it either as A (by disabling or twisting) or drive B (my setup). But if the emu supports two virtual drives, then how do you control each one separately?
And about the loaders: well, indeed, if you don't have enough space on the board, it means it'd need a redesign. As I said, it was more for the sake of discussion :)
Quote from: Gryzor on 08:08, 05 August 10
Thanks for the indications info.
On the UI: I'm still a bit confused after your answer. Maybe I've missed something vital - the emulator can actually emulate two drives? And, I thought the jumpers control the emu's single drive letter, so that you can set it either as A (by disabling or twisting) or drive B (my setup). But if the emu supports two virtual drives, then how do you control each one separately?
And about the loaders: well, indeed, if you don't have enough space on the board, it means it'd need a redesign. As I said, it was more for the sake of discussion :)
Yes it can emulate 2 disk drives.
But on CPC it seems you need to get the DS0 signal inside the computer (non present on the external port. There are only DS1).
So for most CPC users the "Drive B" field on the UI is useless.(if you don'y hack a little your computer. ;) )
Quote from: Jeff_HxC2001 on 08:20, 05 August 10
Yes it can emulate 2 disk drives.
But on CPC it seems you need to get the DS0 signal inside the computer (non present on the external port. There are only DS1).
So for most CPC users the "Drive B" field on the UI is useless.(if you don'y hack a little your computer. ;) )
Ah - there you have it. I still haven't tried it with my ST, so I guess that's where I got confused.
Btw, I don't remember and I don't have my ST in front of me - what kind of cable do you need?
Quote from: Gryzor on 08:08, 05 August 10
And about the loaders: well, indeed, if you don't have enough space on the board, it means it'd need a redesign. As I said, it was more for the sake of discussion :)
Put all features in the device can be good. But don't forget a very important factor :
The final price !!!
Add a more powerful MCU with more ram will increase the final price and make the device harder to build (and probably more expensive to assemble). How many people will buy this if the price go higher than 100 euros ?
Use of an overkill solution is the easy way but also the expensive way ;) .
I think an ABBA switch should do the job here.
Btw, is it only me or does the converter program always crashes after a while when doing batch jobs?
Win7, 64x...
Hm, I think it's on certain images (I attach one). But it happens too often, so you can't really user it for a big collection...
Thank you jeff for your reply, I had read that the TRS 80 model one did not have a data separator, so I was hoping that it was not really necessary.
Quote from: Gryzor on 11:29, 05 August 10
Btw, is it only me or does the converter program always crashes after a while when doing batch jobs?
Win7, 64x...
Hm, I think it's on certain images (I attach one). But it happens too often, so you can't really user it for a big collection...
Could send me these problematic images ?
(http://hxc2001.free.fr/img/imiel.jpg)
Oops sorry I forgot to attach. Here are a couple...
Quote from: Gryzor on 13:09, 05 August 10
Oops sorry I forgot to attach. Here are a couple...
Bug found, and corrected (i hope ;-) )
Please give me a feedback with this beta version :
http://hxc2001.free.fr/floppy_drive_emulator/HxCFloppyEmulator_soft_beta.zip
Ooh! Already? Let's test it...
Yup! It works :) Btw, it took exactly one minute to convert 412 files that resided on an external USB disk. Pretty quick!
Thanks!
A couple of minor suggestions for the CPC interface:
-It is possible to jump to a position after the end of a file list. Ideally it should stop you at the last entry...
-Esc (or maybe another button) should probably be mapped to "dir up". This would save time when in long directories...
-It'd be great if the folder view had multiple columns!
That's about it. Working like a charm!
-oh, except for one thing: every other time the CPC can't read the disk inserted. I have to power the board off and then back on for it to be read...
***Request***
The versions of Discology that I have at hand run through |CPM. But CPM tries to read drive A. Anyone has a version of Discology (v5 preferably?) that runs normally and thus can be loaded through HxC? Thanks in advance!
Quote from: Gryzor on 07:52, 05 August 10
... Also, on the interface, there must be a misunderstanding somewhere... according to the UI, it keeps inserting images to "Drive A" though I have set it up to be Drive B.
Jeff already expained about the drive selector but ..
just wanted to mention that all Amstrad users should remember to tick the "disable disc drive selector" option when they make their config file, to avoid getting the selector that has no purpose (on amstrads).
(http://img18.imageshack.us/img18/7464/lastoz.jpg)
Cheers, Cholo, nice tip. However, Jeff (in his README files) says to use toe provided CFG file with the CPC manager software... I hope there's not something special in it?
Is this a subtle difference with the 6128+ then, or am I missing something? I've removed the dead 3" drive from mine, but still have the HxC on the external port (it was easier to get a cable) and it functions fine as both drive A and B.
Ok, found a small problem: I tried to load the latest Color Lines release, and it says "File error-Bad FAT". This is because I forgot to convert it. However, the board enters a loop and there's nothing you can do to escape! I had to remove the SD and delete the files on the PC to be able to proceed...
Also, why is it that, apparently, folders and files are listed by Modified Date? Wouldn't it make more sense to have it done alphabetically?
Cheers
Gryzor
Quote from: Gryzor on 17:53, 05 August 10
***Request***
The versions of Discology that I have at hand run through |CPM. But CPM tries to read drive A. Anyone has a version of Discology (v5 preferably?) that runs normally and thus can be loaded through HxC? Thanks in advance!
What you can do is use XD-DOS. This DOS allows the command ICPM,2 which boots from drive B. You can boot CP/M in fact from a 0.7 MB disc ;-)
The ICPM,2 may also work for Discology, try it.
Hmm.... I don't even have XD-DOS, let alone on a ROM...
|CPM,2 gives a Drive A read fail!?!
Ok... a potentially serious problem?
After the problems with the latest Color Lines version that I mentioned above, I deleted the files, and I also rewrote AUTOBOOT.hfe and HXCSDFE.cfg from the original CPC Manager archive.
The board is recognized fine, I run"HXC, it starts loading and then (when it switches to mode 2)... it gives me a Drive A Disc missing error!!!!
If I Cancel it says "Bad Signature - HxC Floppy Emulator Not Found (0)"! :(
Any ideas?
Thanks
T
PS The board's screen doesn't give any indication, I think it continues trying to read the file...
I had similar issues with HXC.exe and the HxCSDInterface. The HxCSDInterface 'has' to be set as Drive A (via the IDx jumper settings), whilst this works by forcing it to be 'Drive A', I can only ever see 'Drive A' and not 'Drive B'.
So, if I load HXC, and insert abc.hfe into Drive A and def.hfe into Drive B. I will always see abc.hfe, even if I |a:cat or |b:cat.
If I physically move the IDx jumper to the top selection then I will always see def.hfe.
I cannot seem to find a common ground where I can see both 'Drive A' and 'Drive B'... without physical jumper movement - pressing the buttons on the device doesn't seem to do anything.
...but then again I may have damaged my board when my (real) cat knocked my equipment off my desk including the HxCSDInterface. (When ordering starts again, I might order a backup HxCSDInterface card - just incase)
Hmmm... the issue is, it worked 100% fine up to last night, with the jumpers in place (Drive B) and all... and it suddenly decided to stop.
It's even weirder, given that I *am* loading the program (hxc.bin) from the SD and it fails to recognize the board!!!
I hope Jeff is not on vacation... :(
Hm, there's a new software and firmware version that went unnoticed:
06/08/2010: HxCFloppyEmulator 1.3.12.0
-> New file Support : SAM Coupé MGT file image support added.
-> New file Support : SAM Coupé SAD file image support added.
-> New file Support : Emu EMAX & Emu EMAX 2 (*.EM1 & *.EM2) file support added.
Note : The operating system image (emaxos.emx) must be present in the same folder than the bank files.
-> New file Support : Ensoniq Mirage file support. (the file must have the *.EDM extension)
-> CPC DSK : Random crash bug corrected.
and:
07/08/2010: Firmware SD HxCFloppyEmulator v1.2.0.0
- Bootloader update :
- Size Improvement.
- ASM-C stack corrected, code optimizations.
Link still has the old name, but leads to firmware 1.2.0.0...
Ouf... more problems.
-I copy HxC_SD_Bootloader_V1_0TOV1_1.upd to a formatted SD.
-I press the left and right buttons, then power up
-I leave the buttons, and the only thing it does is stay powered on, with all three leds and all pixels on... and nothing :(
-After the bootloader update fail, I tried going directly to the firmware update, but still the same: everything just stays lit...
[EDIT]...more problems: I copied a few HFE images along with a HXCSDFE.CFG file just to see if I can at least use it normally. It claims it can't find HXCSDFE.CFG...
Is my board toasted?
Have you tried a different SD card? That was exactly the way mine was behaving with the first card I tried. No amount of reformatting made any difference. Used a different one and it worked straight off.
My answer : http://torlus.com/floppy/forum/viewtopic.php?p=2786#2786
It's easy to corrupt the sdcard (if you removed it during a write on your pc for example...)
So if you get such behavior, try reformat it in FAT32. If this doesn't work try this format tool :
http://www.sdcard.org/consumers/formatter_3/SDFormatterEN2905.zip (http://www.sdcard.org/consumers/formatter_3/SDFormatterEN2905.zip)
(Option -> Format type -> FULL (Erase On) )
And reformat the sdcard in FAT32 after this.
If this doesn't work, try another sdcard.
Quote from: Gryzor on 06:32, 09 August 10
Hmm.... I don't even have XD-DOS, let alone on a ROM...
|CPM,2 gives a Drive A read fail!?!
Well, the command |CPM,2 boots from drive B. So if there is no disc in B or a non-system formatted you will get a read fail.
However, you need the XD-DOS, because it provides the |CPM,2 command, it's not in the Amsdos.
You can get the XD-DOS in the Wiki.
@Andy: thanks for the tip, mate.
Ok, a second (4GB) SD worked in loading the Manager and it recognized the board ok... will try again updating the bootloader/firmware and buy a few 512MB cards as well
Will report later...
However, why would a card be corrupted so that nto even a format can bring it back?
@TFM: thanks, man... but at this point, with all the paraphernalia on my CPC it's a bit too much also bringing out the old ROM box :D
So, anyhone has a Discology version that doesn't run with |CPM? :)
Hey Gryzor,
I've dumped this DSK from a cracked Discology version 6 that I had on hand by using SamDisk v3... (CPCDiskXP only creates a bad dump due to the Data Corruption error on track 4..) it'll run by typing run"D
but, you can only run it from drive A .. it complains to insert disk in drive A if you run it from the B drive... also, I havent converted it to test on the SD card yet (at least in WinApe when I tested it, actual 6128 CPC just ran the drive motor)... ;-)
also (on topic), my testing with SD Floppy Manager hasn't yet got it working to the point of choosing a disk image, unlike what everyone else is reporting :(
I spent a few hours over the weekend trying out all the combinations of jumpers and ABBA drive switch settings on my CPC 6128 with a few SD cards... and can consistently get an error message if I load the Floppy Manager from Drive A, and a different message when run from Drive B.... maybe someone can load my setup into their SD Floppy emulator and check it for me??? using it normally through the LCD menu and push buttons can run HFE files no problem, I just can't get the Floppy Manager software working on my setup :(
here's the summary: I've run the floppy manager on my FAT32 formatted SD card, using firmware v1.1.3.0, and Floppy Manager v1.3a software and using one of either: SanDisk 2GB Class 2 SD card, SanDisk 4GB Class 2 SDHC card, SanDisk 8GB Class 2 SDHC card, or a SanDisk 4GB Class 4 SDHC Card...
If i run the Floppy manager from Drive A (IDx jumper as first drive, ABBA switch set the external floppy to Drive A, internal 3" set to B drive), the outcome is the application displays on the monitor "Mounting SD card" which then displays at the top of the screen the message "FAT_FS: Error could not load FAT details (-2)!". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is not lit....
If i run the Floppy manager from Drive B (IDx jumper as second drive, ABBA switch set the external floppy to Drive B, internal 3" floppy as the A drive), the outcome is the application displays on the monitor "Init SD floppy" which then displays the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is flashing....
if i test the Floppy manager program with a Lexar 2GB Class 2 SD Card, running it from drive A will display the message on screen "Reading HXCSDFE.cfg" and nothing happens (waited several minutes just to be sure). LCD screen displays "Direct Access LBA: 0000000"
changing the jumper and ABBA switches so that the SD HxC emulator is then set to the B drive, will generate the message "Init SD floppy" which then changes to displaying the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000"
can anyone else try out my settings and HFE game (1943) on their own SD HxC board, and report back what happens?
cheers!
Quote from: Gryzor on 06:56, 10 August 10
@Andy: thanks for the tip, mate.
Ok, a second (4GB) SD worked in loading the Manager and it recognized the board ok... will try again updating the bootloader/firmware and buy a few 512MB cards as well
Will report later...
However, why would a card be corrupted so that nto even a format can bring it back?
@TFM: thanks, man... but at this point, with all the paraphernalia on my CPC it's a bit too much also bringing out the old ROM box
So, anyhone has a Discology version that doesn't run with |CPM?
@Gryzor,
The communication to the SD CARD is done using the SPI protocol, this is a serial protocol which "should" be able to ramp up/down through a whole range of speeds. As I had absolutely nothing to do with the HxC design, I can't tell you which speed Jeff chose to communicate with the cards, but my own experiences of SPI SD communication was that some lesser known cards can have issues if the speed changed to quickly or if you used particular speeds (usually the lower range of the speed scale) that they didn't like. The card may be perfectly good on other devices, just it doesn't work well at the speeds the HxC uses. I try to stick to SanDisk or other well known brands, that stick to the exact specs.
But Jeff can probably give you more details of exactly what the HxC uses.
Bryce.
Quote from: Bryce on 14:21, 10 August 10
@Gryzor,
The communication to the SD CARD is done using the SPI protocol, this is a serial protocol which "should" be able to ramp up/down through a whole range of speeds. As I had absolutely nothing to do with the HxC design, I can't tell you which speed Jeff chose to communicate with the cards, but my own experiences of SPI SD communication was that some lesser known cards can have issues if the speed changed to quickly or if you used particular speeds (usually the lower range of the speed scale) that they didn't like. The card may be perfectly good on other devices, just it doesn't work well at the speeds the HxC uses. I try to stick to SanDisk or other well known brands, that stick to the exact specs.
But Jeff can probably give you more details of exactly what the HxC uses.
Bryce.
Hm... this is interesting. Actually today I got out and got me a 2GB Kingston one (with a very nice adaptor: no longer a micro->mini-standard thing, just a USB adaptor!), and againt he same problems... the card of course is working perfectly on my PC and netbook, it's just the board that refuses to cooperate. In the meantime, an older Kingston SD (4GB) that I had in my Dingoo works just fine (but read on). I just hope the Emulator does not chew through SD cards, this would be uneconomical...
Quote from: archcosmo on 14:12, 10 August 10
Hey Gryzor,
I've dumped this DSK from a cracked Discology version 6 that I had on hand by using SamDisk v3... (CPCDiskXP only creates a bad dump due to the Data Corruption error on track 4..) it'll run by typing run"D
but, you can only run it from drive A .. it complains to insert disk in drive A if you run it from the B drive... also, I havent converted it to test on the SD card yet (at least in WinApe when I tested it, actual 6128 CPC just ran the drive motor)... ;-)
I much appreciate it mate! Of course it's a pity it doesn't work from |b... What would you guys suggest as the best method of copying dsk images from the Emulator (drive B) to a real disk in Drive A?
I will test your config tomorrow morning, as I'm leaving in a while. But, could you also attach the hfe file?
Cheers
Gryzor
PS Although the card I'm using now seems to be working fine, I'm getting the LBA messages (starting from 0000000 and building up). What does that mean?
PS2 You mention red and green LEDs? Mine only has red ones!!!
Quote from: Gryzor on 18:09, 10 August 10
Hm... this is interesting. Actually today I got out and got me a 2GB Kingston one (with a very nice adaptor: no longer a micro->mini-standard thing, just a USB adaptor!), and againt he same problems... the card of course is working perfectly on my PC and netbook, it's just the board that refuses to cooperate. In the meantime, an older Kingston SD (4GB) that I had in my Dingoo works just fine (but read on). I just hope the Emulator does not chew through SD cards, this would be uneconomical...I much appreciate it mate! Of course it's a pity it doesn't work from |b... What would you guys suggest as the best method of copying dsk images from the Emulator (drive B) to a real disk in Drive A?
I will test your config tomorrow morning, as I'm leaving in a while. But, could you also attach the hfe file?
Cheers
Gryzor
PS Although the card I'm using now seems to be working fine, I'm getting the LBA messages (starting from 0000000 and building up). What does that mean?
PS2 You mention red and green LEDs? Mine only has red ones!!!
Gryzor : your first sdcard didn't work anymore because you have removed it during a write (during the dead loop bug-> i will correct this). So some sectors are probably bad or locked.
Please make this : make a big zip file (~512MB), copy it to the sdcard.Once done remove the sdcard and reinsert it (to kill all memory cache), and then try to copy back to your pc. After this try to unpack this zip file.
Quote from: archcosmo on 14:12, 10 August 10
Hey Gryzor,
I've dumped this DSK from a cracked Discology version 6 that I had on hand by using SamDisk v3... (CPCDiskXP only creates a bad dump due to the Data Corruption error on track 4..) it'll run by typing run"D
but, you can only run it from drive A .. it complains to insert disk in drive A if you run it from the B drive... also, I havent converted it to test on the SD card yet (at least in WinApe when I tested it, actual 6128 CPC just ran the drive motor)... ;-)
also (on topic), my testing with SD Floppy Manager hasn't yet got it working to the point of choosing a disk image, unlike what everyone else is reporting :(
I spent a few hours over the weekend trying out all the combinations of jumpers and ABBA drive switch settings on my CPC 6128 with a few SD cards... and can consistently get an error message if I load the Floppy Manager from Drive A, and a different message when run from Drive B.... maybe someone can load my setup into their SD Floppy emulator and check it for me??? using it normally through the LCD menu and push buttons can run HFE files no problem, I just can't get the Floppy Manager software working on my setup :(
here's the summary: I've run the floppy manager on my FAT32 formatted SD card, using firmware v1.1.3.0, and Floppy Manager v1.3a software and using one of either: SanDisk 2GB Class 2 SD card, SanDisk 4GB Class 2 SDHC card, SanDisk 8GB Class 2 SDHC card, or a SanDisk 4GB Class 4 SDHC Card...
If i run the Floppy manager from Drive A (IDx jumper as first drive, ABBA switch set the external floppy to Drive A, internal 3" set to B drive), the outcome is the application displays on the monitor "Mounting SD card" which then displays at the top of the screen the message "FAT_FS: Error could not load FAT details (-2)!". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is not lit....
If i run the Floppy manager from Drive B (IDx jumper as second drive, ABBA switch set the external floppy to Drive B, internal 3" floppy as the A drive), the outcome is the application displays on the monitor "Init SD floppy" which then displays the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is flashing....
if i test the Floppy manager program with a Lexar 2GB Class 2 SD Card, running it from drive A will display the message on screen "Reading HXCSDFE.cfg" and nothing happens (waited several minutes just to be sure). LCD screen displays "Direct Access LBA: 0000000"
changing the jumper and ABBA switches so that the SD HxC emulator is then set to the B drive, will generate the message "Init SD floppy" which then changes to displaying the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000"
can anyone else try out my settings and HFE game (1943) on their own SD HxC board, and report back what happens?
cheers!
Which computer are you using ? 464 6128,6128+ ?
Quote from: Gryzor on 18:09, 10 August 10
PS Although the card I'm using now seems to be working fine, I'm getting the LBA messages (starting from 0000000 and building up). What does that mean?
This means that all is ok :
LBA=
Logical block addressing -> Address of the sdcard sector actually read or writehttp://en.wikipedia.org/wiki/Logical_block_addressing
Quote from: Gryzor on 18:09, 10 August 10
PS2 You mention red and green LEDs? Mine only has red ones!!!
Yes some changes during the production.
Quote from: Jeff_HxC2001 on 18:51, 10 August 10
Gryzor : your first sdcard didn't work anymore because you have removed it during a write (during the dead loop bug-> i will correct this). So some sectors are probably bad or locked.
Please make this : make a big zip file (~512MB), copy it to the sdcard.Once done remove the sdcard and reinsert it (to kill all memory cache), and then try to copy back to your pc. After this try to unpack this zip file.
Thanks for all the support mate... it's much, much appreciated.
I never remove a card while the board is still on. And I don't turn it off while it's obviously reading or writing something -but then again, I'm not sure what 'obviously' means here.
About the file method you suggested: this is all done on the PC, right? But what will it achieve?
Also, thanks about the LBA clarification. I hadn't seen it with older firmware versions, and I did guess that it probably didn't mean anything was wrong, but thought I'd ask.
Shame, I'd like some yellow and green blinkies... :D
Off to a date now, already running late. See what your board does? Kills social life!
Quote from: Gryzor on 19:01, 10 August 10
Thanks for all the support mate... it's much, much appreciated.
I never remove a card while the board is still on. And I don't turn it off while it's obviously reading or writing something -but then again, I'm not sure what 'obviously' means here.
Quote from: Gryzor
After the problems with the latest Color Lines version (it wouldn't load the files, then it'd try to auto-load the bad files upon rebooting and thus enter a loop)...
The device enter in a loop and many operation are done on the sdcard. You have removed or cut the power supply at this moment.
Quote from: Gryzor on 19:01, 10 August 10
About the file method you suggested: this is all done on the PC, right? But what will it achieve?
Yes on PC. If you got a bad zip file (crc error or something else), you have some dead sectors on the sdcard.
Quote from: Gryzor on 19:01, 10 August 10
Also, thanks about the LBA clarification. I hadn't seen it with older firmware versions, and I did guess that it probably didn't mean anything was wrong, but thought I'd ask.
Strange. This message was there since the direct access mode support.
Quote from: Gryzor on 19:01, 10 August 10
Off to a date now, already running late. See what your board does? Kills social life!
;)
Firmware update !
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_firmware.zip
Updated to 1.2.0.0 (took a whole hour of reformatting but finally worked, lol). Also helped that i got a 1GB Kingston card (the old Lexar 256mb one seemed to give me all but troubles). Anyways everything works now even the Manager on my 464+DDI (DF0)+HxC(DF1) and boot from either drive :)
Hints about flashing the 1.2.0.0 firmware: While flashing the bootloader.upd first keep an eye on the 3rd led and if it flashes a lot very quickly then its reading from the SD card (aka its updating). After its done its hard to know if its actually flashed as it behaves a bit like its empty. But just go ahead and flash the actual 1.2.0.0 then as its most likely flash ok, and is waiting for the firmware to be flashed. Again looking at the 3rd led when flashing .. if you dont get a full 1-2 sec of rapid flashing then something is probably wrong and you need to reformat and try again.
Quote from: Cholo on 21:58, 10 August 10
Updated to 1.2.0.0 (took a whole hour of reformatting but finally worked, lol). Also helped that i got a 1GB Kingston card (the old Lexar 256mb one seemed to give me all but troubles). Anyways everything works now even the Manager on my 464+DDI (DF0)+HxC(DF1) and boot from either drive :)
Hints about flashing the 1.2.0.0 firmware: While flashing the bootloader.upd first keep an eye on the 3rd led and if it flashes a lot very quickly then its reading from the SD card (aka its updating). After its done its hard to know if its actually flashed as it behaves a bit like its empty. But just go ahead and flash the actual 1.2.0.0 then as its most likely flash ok, and is waiting for the firmware to be flashed. Again looking at the 3rd led when flashing .. if you dont get a full 1-2 sec of rapid flashing then something is probably wrong and you need to reformat and try again.
Some important points :
-> The actual firmware version is V1.2.0.1
->
Do not cut the power supply during the bootloader programming !!!! The bootloader programming is done when 2 leds are blinking, not before ! (Sdcard access led and Floppy Access led). To be sure wait 1 minutes.
Here the readme.txt
Quote
SDCard HxC Floppy Emulator Update procedure :
For users with the firmware V1.2.0.0 or above jump to the step 2) directly
1) Bootloader update (for users with a firmware below the version 1.2.0.0)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! Warning : DO NOT CUT the power supply of the board during the bootloader programming ! !!!
!!! In case of power loss, the device may be unusable and need a factory reprogramming. !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-> Copy the new bootloader file (HxC_SD_Bootloader_V1_0TOV1_1.upd) to a freshly formated FAT32 SDCard.
-> Insert the SDCard into the emulator
-> Press Left and Right buttons before power up and keep it pressed at least 1 seconds at power up.
-> Wait some seconds. When 2 leds are blinking (Sdcard access led and Floppy Access led) it's done !
(to be sure wait 1 minutes before removing the power supply).
After this the firmware must be flashed. (->step 2 Firmware update)
2) Firmware update
-> Copy the new firmware file (*.upd) to a freshly formated FAT32 SDCard.
-> Insert the SDCard into the emulator
-> Press Left and Right buttons before power up and keep it pressed at least 1 seconds at power up.
-> Wait some seconds .... its done !
Note 1:
The file must be unfragmented on the sdcard and must be in the first part of the root directory.
For these reasons it is recommended to use a freshly formatted FAT32 SDCard, otherwise you may get the error 4 or 6 (see note 2).
Note 2:
Bootstrap LED error messages:
Error 1 : (blink 1 time and 2 seconds pause cycle) No entry point (->no software flashed)
Error 2 : (blink 2 time and 2 seconds pause cycle) SDCard init error.
Error 3 : (blink 3 time and 2 seconds pause cycle) FAT error.
Error 4 : (blink 4 time and 2 seconds pause cycle) UPD File not found!
Error 5 : (blink 5 time and 2 seconds pause cycle) Bad UPD File header! (bad file)
Error 6 : (blink 6 time and 2 seconds pause cycle) Bad data crc! (file corrupt)
Error 7 : (blink 7 time and 2 seconds pause cycle) Bad data size!
Error 8 : (blink 8 time and 2 seconds pause cycle) Write error (Pic flash error)
Jeff / HxC2001
Well, if the device entered an infinite loop then indeed I cut the power while access was on. But this is a design issue, because you just can't stop the loop, can you? I saw in 1.2.0.1 (gaaaa! Got to update! I'm turning obsessive-compulsive!) that you escape the loop by reverting to autoboot.hfe. But what Autoboot is not present?
I think it'd be best if the board just stopped reading the bad file after a number of tries (and you could make this an option in the config file to be set by the user). What do you think? :)
Still, this doesn't explain why the brand new card had problems... I'll try the method you suggested tomorrow, but I'll try to fill the entire 2GB disk with a file. Also, I guess you don't actually need to zip a file, just a program to calculate the checksum I guess?
Btw, with the latest firmware and/or manager, when you switch pages by reaching the end of a page or pressing left/right, it takes a LOT of time to become responsive after displaying the rest of the list... I think the interface would greatly benefit if it used multiple columns and devoted mor space to the file list instead of losing half the lower screen to the instructions and logo...
But, in case I appear to be complaining a lot, I just have to say: I LOVE THIS BOARD and I haven't regretted buying it for a moment...
Quote from: Gryzor on 06:56, 10 August 10
@TFM: thanks, man... but at this point, with all the paraphernalia on my CPC it's a bit too much also bringing out the old ROM box :D
So, anyhone has a Discology version that doesn't run with |CPM? :)
Maybe you should use your old ROM box :D ... because there is a ROM version of Discology. In case you don't find it on the net, and in case you really like to use it, then PM me. I have to search & find it first.
Nah - I'm trying to keep the setup lean... just want to copy some disks!
I'll probably use Oddjob to copy a Discology image to Drive A (can it do that?)
Jeff, I just covered every byte of the 'bad' SD with a rar file and it decompressed just fine after copying it back to the PC... If you're interested I could maybe mail you the SD card to check?
[Edit] here (http://translate.google.com/translate?prev=&hl=uk&ie=UTF-8&u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&sl=ru&tl=en&history_state0=) is a tool to test an SD card... gonna try and use it now.
[Edit2] flashnul.exe x: -T returns no errors...
Quote from: archcosmo on 14:12, 10 August 10
Hey Gryzor,
also (on topic), my testing with SD Floppy Manager hasn't yet got it working to the point of choosing a disk image, unlike what everyone else is reporting :(
I spent a few hours over the weekend trying out all the combinations of jumpers and ABBA drive switch settings on my CPC 6128 with a few SD cards... and can consistently get an error message if I load the Floppy Manager from Drive A, and a different message when run from Drive B.... maybe someone can load my setup into their SD Floppy emulator and check it for me??? using it normally through the LCD menu and push buttons can run HFE files no problem, I just can't get the Floppy Manager software working on my setup :(
here's the summary: I've run the floppy manager on my FAT32 formatted SD card, using firmware v1.1.3.0, and Floppy Manager v1.3a software and using one of either: SanDisk 2GB Class 2 SD card, SanDisk 4GB Class 2 SDHC card, SanDisk 8GB Class 2 SDHC card, or a SanDisk 4GB Class 4 SDHC Card...
If i run the Floppy manager from Drive A (IDx jumper as first drive, ABBA switch set the external floppy to Drive A, internal 3" set to B drive), the outcome is the application displays on the monitor "Mounting SD card" which then displays at the top of the screen the message "FAT_FS: Error could not load FAT details (-2)!". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is not lit....
If i run the Floppy manager from Drive B (IDx jumper as second drive, ABBA switch set the external floppy to Drive B, internal 3" floppy as the A drive), the outcome is the application displays on the monitor "Init SD floppy" which then displays the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000", and the green LED is flashing, orange LED is flashing....
if i test the Floppy manager program with a Lexar 2GB Class 2 SD Card, running it from drive A will display the message on screen "Reading HXCSDFE.cfg" and nothing happens (waited several minutes just to be sure). LCD screen displays "Direct Access LBA: 0000000"
changing the jumper and ABBA switches so that the SD HxC emulator is then set to the B drive, will generate the message "Init SD floppy" which then changes to displaying the message "ERROR: Floppy Access error! [64]". The LCD display on the SD HxC displays "Direct Access LBA: 0000000"
can anyone else try out my settings and HFE game (1943) on their own SD HxC board, and report back what happens?
cheers!
Mate, just tried 1943 with your settings (I didn't realize you had included the hfe image). It runs beautifully with my setup (Emulator set as drive B through jumper)... let me know if I could do/test anything else for you!
Quote from: Gryzor on 06:32, 11 August 10
Nah - I'm trying to keep the setup lean... just want to copy some disks!
I'll probably use Oddjob to copy a Discology image to Drive A (can it do that?)
Jeff, I just covered every byte of the 'bad' SD with a rar file and it decompressed just fine after copying it back to the PC... If you're interested I could maybe mail you the SD card to check?
Yes if you want:
(http://hxc2001.free.fr/img/myaddress.jpg)
You got it, one micro-SD on its way tomorrow morning. Btw, you do have an SD adaptor, don't you? I guess everyone and their dog has a few of them lying around by now, but I thought I'd make sure...
Quote from: Jeff_HxC2001 on 18:53, 10 August 10
Which computer are you using ? 464 6128,6128+ ?
Quote from: Gryzor on 08:11, 11 August 10
Mate, just tried 1943 with your settings (I didn't realize you had included the hfe image). It runs beautifully with my setup (Emulator set as drive B through jumper)... let me know if I could do/test anything else for you!
hi Jeff,
I've been using the SD HXC emulator just on my CPC 6128
do you have a short list of SD cards that you've personally tested with the floppy emulator during it's development? it just seems strange to be getting similar error messages with a few different kinds of SanDisk SD cards (purchased brand new from the retail store, and then reformatted using the SD card formatter) when others are reporting no issues after reformatting their SD card
I haven't yet updated my SD HxC boards (I have two, the red PCB variant from the 1st batch sold via ebay, and a black PCB from Lotharek's 2nd batch) to the latest firmware version, but I'll do it over the weekend, reformat some SD cards and try it out again :)
can anyone else report back on what SD Card (brand, capacity and Class if possible) they're using successfully in their SD HXC along with the Floppy Manager - it'll satisfy my curiosity with what's working for other people on the forum! :)
Hi Gryzor
thanks for checking - I appreciate it! though a little disappointed that i can't play it the same way you've just done! lol
cheers
Ok... been trying to make the board appear as Drive A and I'm hitting various walls... could someone explain to me in detail what exactly must be done?
By 'detail' I mean:
-hxcfloppyemulator.cfg
-HXCSDFE.CFG
-jumpers
-internal floppy cable (can I just remove the power supply?)
Thanks!
Gry
now you know why the crocodile-clip scenario came about ;D
.CFG files I'm using are the one's that came with the FloopyManager software download - I have not modified them.
okay, are you attempting to replace the internal 3" drive in a 6128? or have the HxC plugged into the 'disc drive 2' flat edge connector out the back of the 6128?
I was able to successfully plug the HxC into the 'disc drive 2' flat edge connector and operate as Drive A with the following jumper settings:
. . .
. [.] .
. [.] .
To get it to work internally to replace the 3" drive I had to set the jumper to be: (the jumpers are described in the PDF but it took me a while to actually understand what it meant):
. . .
[.] . .
[.] . .
The flaw I found with having the HxC replacing the internal drive is that I needed to make a new 26pin -> 34pin cable (I documented the pin matching in a different thread and will update the wiki page).
It works well for me as Drive A (I just cannot get it to be Drive B unless I physically unplug the jumper above and move it to the top - I can live without that for the moment)
Quote from: Gryzor on 10:48, 13 August 10
Ok... been trying to make the board appear as Drive A and I'm hitting various walls... could someone explain to me in detail what exactly must be done?
By 'detail' I mean:
-hxcfloppyemulator.cfg
-HXCSDFE.CFG
-jumpers
-internal floppy cable (can I just remove the power supply?)
Thanks!
Gry
it's only a jumper and cable problem.
Please read the user manual page 9 :
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_User_Manual.pdf
Quote
Emulator as the first disk drive
Note : In this case the internal floppy
disk drive must be disabled.
To do this you can connect wire 23 to the
ground (wire 24), or simply unplug the
floppy cable from the internal disk drive.
@ynot: actually I'm trying to make the board, connected on the Drive 2 edge connector, to work as drive A, having first disabled the internal drive. As I said, even having completely unplugged the internal drive (ribbon/power or only power), I can't get it to work... it gives read error problems (with the classic sound coming from the board: gh-ghhhhh...ghhhhh..... gh. gh-ghhhhh....ghhhhh... you get the idea :D).
@Jeff: yes, of course I've read the manual and I went for disabling the internal drive altogether, that's why I asked for further directions (btw, ynot.zero, there are four jumper positions, not three, but I get what you mean).
Question: can I just connect the board to the internal ribbon/power supply and having it hanging out the back of the machine?
....oh! you're connecting to the external connector, in that case, find yourself an old PC internal cable and just short the pins with a couple of wires as mentioned. I originally did this very successfully. pins 11&12 and 33&34 - scroll down to the 'Setting the READY signal' section
http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5"_drive_to_a_CPC6128/664 (http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5%22_drive_to_a_CPC6128/664)
I'm intrigued that you mention connecting your board to the internal ribbon?! that's the 26pin connector, no? as to the power - yes, I re-used the PSU from the internal 3" drive (you swap the two outside wire around as mentioned in the PDF)
I'm not sure why another cable should be used? I did think that, as Jeff's manual mentions, either pin shorting OR drive disabling should work? Oh well, never mind - I'll use that as motivation to replace the failing belt again :D Thanks for your input, however...
About the ribbon that you mentioned -that's why I'm asking: actually I'm at a neighbor's apartment playing on his 360 and don't have my CPC with me (of course), and it was bugging me - I *think* the internal ribbon is more narrow but I'm not sure, but you made that clear :)
Cheers
T
Quote from: Gryzor on 19:02, 13 August 10
I'm not sure why another cable should be used? I did think that, as Jeff's manual mentions, either pin shorting OR drive disabling should work? Oh well, never mind - I'll use that as motivation to replace the failing belt again :D Thanks for your input, however...
About the ribbon that you mentioned -that's why I'm asking: actually I'm at a neighbor's apartment playing on his 360 and don't have my CPC with me (of course), and it was bugging me - I *think* the internal ribbon is more narrow but I'm not sure, but you made that clear :)
Cheers
T
you must do a pin shorting
AND disable the internal drive.
I put again the text of the user manual :
Quote
Emulator as the first disk drive
Note : In this case the internal floppy
disk drive must be disabled.
To do this you can connect wire 23 to the
ground (wire 24), or simply unplug the
floppy cable from the internal disk drive.
Quote from: ynot.zer0 on 17:46, 13 August 10
....oh! you're connecting to the external connector, in that case, find yourself an old PC internal cable and just short the pins with a couple of wires as mentioned. I originally did this very successfully. pins 11&12 and 33&34 - scroll down to the 'Setting the READY signal' section
http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5"_drive_to_a_CPC6128/664 (http://www.cpcwiki.eu/index.php/Guide_on_how_to_connect_a_3.5%22_drive_to_a_CPC6128/664)
The HxC Floppy Emulator emulate correctly the Ready signal so shorting pin 33&34 is useless.
The only pins to sort is 11&12 (or pins 23&24 if you take the floppy cable order).
Quote from: Gryzor on 23:04, 10 August 10
Btw, with the latest firmware and/or manager, when you switch pages by reaching the end of a page or pressing left/right, it takes a LOT of time to become responsive after displaying the rest of the list... I think the interface would greatly benefit if it used multiple columns and devoted mor space to the file list instead of losing half the lower screen to the instructions and logo...
But, in case I appear to be complaining a lot, I just have to say: I LOVE THIS BOARD and I haven't regretted buying it for a moment...
An important news : Norecess are actually working on the file manager : I just got its version, and the soft are now smaller (faster start and Eprom compatible), and a lot faster.
Like you i am impatient to present you the final version ;) .
Quote from: Jeff_HxC2001 on 19:40, 13 August 10
you must do a pin shorting AND disable the internal drive.
I put again the text of the user manual :
Quote
Emulator as the first disk drive
Note : In this case the internal floppy
disk drive must be disabled.
To do this you can connect wire 23 to the
ground (wire 24), or simply unplug the
floppy cable from the internal disk drive.
Erm... but... first you say that you must do
both the shorting
and the drive removal, and then you quote the manual (I'm sleeping with it these days :D ) where it says
OR, not
and!!
I guess that after all the correct procedure requires
and...
Can't wait for the new manager version :) Actually I read
Epson compatible in your description :D
A bit of teasing for HxC Floppy Emulator owners : as Jeff HxC2001 said, in few days, there will be a ROM version of the manager, as also a standard binary to be put in AUTOBOOT.HFE, featuring major speed enhancements and much more !
You will enjoy it for sure.
Hello mate!
Ever since Jeff mentioned it, I've set his webpage to auto-reload every half-hour in Opera :D :D :D
Just a question: when you say "Rom version", does this mean it will be in the form of a firmware update?
If you want any beta-testing please do consider me :)
Can't wait!
Cheers
Gryzor
By ROM version, I mean traditional CPC rom version to be put on boards like Ramcard extensions etc. same things like Maxam, Protext, etc. from Arnor.
This means that |HXC launch the manager without loading from disc. Fast.. very fast.
Send me your mail at arnaud.storq gdfjkghdfjkhgdfjkhgjksdfhgjksdfh gmail.com ; you can be a beta-tester.
Ohhh darn... gotta find my ROM board, and also someone to blow an EPROM for me... :D
BTW - I want to publicly congrat Jeff (HxC2001) for providing the sources ; for not being selfish in his project and being that open-minded. This really makes the HxC Floppy Emulator a wonderful product, not just a simple port for any retro machines but a perfect adaptation to CPC machines !
Trust me, he really want the best and I have been really impressed by his technical support so far. Probably the best "con" of this thread I guess :P
Yeah... Jeff has proved to be very helpful and meticulous. I must really give him my congratulations for his efforts to help and for his contributions even here, even though he's got his own forum. Talk about after-sales support! :)
Hi, maybe someone of you can help me. I'm thinking of buying two of the read/write HxC floppy emulators. But I've to questions of major interrest:
- Has somebody already tested FutureOS with the HxC? If it is not compatible, I wouldn't need it. Would be great if I can get informations if it works together or not.
- Where can I get the source of the CPC-Image-Manager, you've been talking in the posts before.
I really would apprreciate any kind of help / information.
I'll try and test it today... do you have, perhaps, a latest, unreleased version you'd like to send me?
Cheers
T
Let us know how it works for you.. no new internal version yet.
And the sources are not released. I let Jeff to decide whatever he wants with that... :)
(I just helped him in having a better CPC product..)
@TFM: oops, sorry man, I forgot it runs on ROM... I don't have my board at hand :(
Gryzor : did you try the disc-based version ?
Yes, feedback coming your way later in the afternoon :)
Quote from: Gryzor on 07:03, 19 August 10
I'll try and test it today... do you have, perhaps, a latest, unreleased version you'd like to send me?
Cheers
T
Hehe, not at the moment, but if ever you get if first ;-)
Well, you can give Giana a try or let's make it easy. Try to display the directory of any disc. If the DIRectory can be viewed, then the disc-part should work properly.
Quote from: Gryzor on 15:41, 19 August 10
@TFM: oops, sorry man, I forgot it runs on ROM... I don't have my board at hand :(
Well, patience is a virtue. I have to learn it every day new :-)))
Quote from: norecess on 10:48, 19 August 10
And the sources are not released. I let Jeff to decide whatever he wants with that... :)
(I just helped him in having a better CPC product..)
It would be absolutely great to have the sources. Because... Then you can switch to another disc in your own programs/apps./demos/games and you DON'T have to bother the user with that "TURN DISC PLEASE" - What a easy this would be ;-))) I'm really looking forward to a release of the code. At least the part how to select an disc-image.
Ahah! Good luck in integrating such "turn disc". :)
First, the manager links with Fatlib, which is written in C, so it means all your programs would have to be written in C too.
Second, let's admit you are ready to support the extra 16Kb-20Kb for FAT32 management, and that your app is written in C, how would you switch to the second HFE ? I mean, where would be its location / what would be the filename ?
So.. forget it. Sources would not help you here, sorry :-(
More seriously, the manager has to be seen as a tool to help editing slots from HFEs located on SDCard, nothing more.
Don't expect introducing specific HxC features in your own programs, it's not the aim.
Quote from: norecess on 20:54, 19 August 10
More seriously, the manager has to be seen as a tool to help editing slots from HFEs located on SDCard, nothing more.
Don't expect introducing specific HxC features in your own programs, it's not the aim.
Ok, no need to explode. Neither I have the HxC (now) not do I have the source-code.
But like I know (and correct me shouting if I'm wrong) there is a CPC software which can be used to select different disc images. Right?
So that's all I need, a possiblility to switch disc-images by software!
Did you get it ;)
Ok, last night I dug out my RRB (lying in a box buried under month of paperwork) and did some test with FutureOS .7 (ROM).
With the old firmware I still had on my HxC SD seeking would not work under FOS. A directory listing would show when the CAT command under AmsDos was issued before starting FOS but nothing more.
So I updated my HxC SD with the latest firmware and... suddenly everything works. I was able to read FutureView III and start the movie player. If there is more I can test I now have the setup in place (and even cleaned my desk ;))
I also realized that the Midline Process demo works now. This trackloading demo did not work with the old firmware, so the FDD emulation has definitely improved. I did not try any heavily copy protected titles yet, but even if they don't work the HxC is a really nice piece of hardware. I especially like the CPC hfe image selector which I also tried for the first time last night. Much easier than navigating the filesystem on the LCD, although I could use more than 7 slots. Looking forward to the ROM version of the manager application. Beta request is on its way. :)
Quotethere is a CPC software which can be used to select different disc images. Right?
Yes, there is one, and it's called HxC Floppy Emulator Manager. The V2 is about to be released soon! :)
Quotealthough I could use more than 7 slots
Next version is featuring 16 slots management (including the AUTOBOOT.HFE file).
"16 slots will be enough for everybody" (c) bill gates/1981
Quotethe HxC is a really nice piece of hardware
Yes, it is. I had some initial concerns regarding disc images navigation using the hardware's buttons, but since we can select images through a software it perfectly fits my needs!
@Nurgle: Thank you very very very much for testing!!! Glad that everything is running well (at least with the new firmware). :) :) :)
@No recess: Now we come together. ::) So the HxC Floppy Emulator Manager can change disc-images (you call them slots). And that's all that is needed to "turn a disc" around. And this software should be released. 8)
[/size]QuoteSo the HxC Floppy Emulator Manager can change disc-images (you call them slots)
No, you don't understand. HxC has 16 slots, in which the user can assign disc-image in them using the manager. Once you leave the manager, you can then use the left and right buttons to navigate through the slots.Buy the hardware first, then you will understand. :)
Quote from: norecess on 20:41, 20 August 10
Buy the hardware first, then you will understand. :)
Clever marketing, respect! :laugh: ;)
The new version is available on Jeff's website :
http://hxc2001.free.fr/floppy_drive_emulator/index.html#download
Featuring :
- 16 slots instead of 8
- fast to load (file is 15Kb now)
- ROM/disc version
- more HFE files displayed on screen
- show current folder
- the interface is now faster to display/clear/etc
- ability to display ALL slots at the same time
- and more..
Screenshot :
https://sourceforge.net/project/screenshots.php?group_id=310120
Is this the same as the beta version?
Yeah. 8)
Quote from: norecess on 20:41, 20 August 10
No, you don't understand.
HxC has 16 slots, in which the user can assign disc-image in them using the manager. Once you leave the manager, you can then use the left and right buttons to navigate through the slots.
Buy the hardware first, then you will understand. :)
Wondeful, so this software can assign a disc-image to a slot. Now imagine I work with only one slot, so I can use the software to assigen any disc-image to this slot (that's what you sayd). So this is like "change disc". Ok?
I don't get the point - why would you do this ?
Quote from: norecess on 02:17, 23 August 10
I don't get the point - why would you do this ?
Ok... you have demo/game/prog (whatever) that is split on several discs (disc-images). Now you usually will get a message like "Inserter disquette numero 3 SVP". So you get this messages and you have to change the disc(-image).
If you would be able to do this by software (change the disc-image for the current slot) you wouldn't bother the user any longer with messages. Everything would work automatically.
Got it? :-X
Yeah, got it ;)
Your solution would implies to :
1) first create a multiple-sided demo/game/demo. Not that easy hehe :laugh:
2) so let's say you created the kickass demo, the user HAS to get the HxC Floppy Emulator working with the CPC (or you probably want to detect it I guess, so you still have to keep compatibility with previous regular disc-based systems)
3) how do you know in which FAT32 folder in the next side-disc image ? it would be evil to tell it's current folder of the current one (and actually, I'm not sure if you get that info of "current dir").
And finally, this is personal opinion, but...
4) I still enjoy watching turn-disc parts. :)
Well, anyway, I think technically you could do what you have in mind but I have many concerns in its realisation. First look at the sources, you will understand (don't forget it has to use a C library "Fatlib").
Oh, people probably did not notice it, but Jeff also release source-code of the manager ; check on his site for more info!
There's also an update for the windows manager, from what I saw?
the new CPC manager is really, really nice... the best feature, of course, is the extra 8 slots. I just wish it was a bit less spartan in its appearance :)
Looking forward to the next version!
Thanks for the feedback!
Removing the original background and switching to command line interface allowed to save space for new features.
I prefer having a cut-featured UI and having more features, than a beautiful UI with limited features.
What do you think about that?
Of course I agree with that - we discussed it already :D
On the other hand, I prefer a useful tool WITH a nice interface ;) How much space would it take to draw a couple of lines? I understand the lack of a loading image, what with loading the program into the VRAM and all, but a kind of screen organization with simple lines would go a long way...
Quote from: norecess on 11:18, 23 August 10
Thanks for the feedback!
Removing the original background and switching to command line interface allowed to save space for new features.
I prefer having a cut-featured UI and having more features, than a beautiful UI with limited features.
What do you think about that?
There is currently something like 800 bytes free.
There are other interesting features planned ; so I guess the UI won't evolve much than the today's one.
I've been meaning to ask you -why is it so big? Of course I don't know the underlying workings of it, but that's why I'm asking... what is there that takes so much space to work?
Btw, in any case, I prefer a *fast* UI over a pretty one.
It's that big because it's using fatlib, a library written in C that has to handle a complete FAT32 management.. and by "big", I was actually amazed by the small size it takes for doing that stuff, but hey :)
Hi 8)
I'm having problem formatting the SD cards. A few weeks ago I bought 3 x "Transcend SDHC 8GB Class (10)", and up to recently these THREE cards has been working perfectly.
I did the updates that came this weekend. I used a "1GB Kingston SD elite pro" card for the updates, and that works. The HxC hardware is now updated to the last firmware (1.3.0.0).
So I decided to reformat one of the Transcend cards, and put everything on a fresh card.
I formatted it using "SD Formatter V2.9.0.5", and then formatted it in windows. The I copied the files on the card in the following order :
1) HXCFE_V1_3_0_0.UPD
2) HXCSDFE.CFG
3) AUTOBOOT.HFE
4) plus a lot of HFE files
On my CPC I get the following message "Reading FAT". That message stays on all the time. So I tried another solution. With the UPD file on the card I tried to update the firmware from the card. Result is the LED blinks 4 times, then a pause and four new blinks. That means it can't find and UPD on the card, and that it can't read the card.
Obviously there is something wrong with the formatting of the card.
So how have I formatted the card (This is going to be detailed, as to find out what I do wrong)
1) Within "SDFormatter V2.9.0.5" I have the following settings for my "Transcend SDHC 8GB Class 10" card :
Format type - "FULL (Erase ON)"
Format Size adjustment - "OFF"
Then "Format" and "OK" (takes 16 min on my computer)
When the format is finished I get the following information:
Volume Information
-File system : FAT32
-Total space = 7.48 GB(8,040,480,768 Bytes)
-Cluster size=32768 Bytes
2) Then I goes to Windows Explorer to format the card :
The following options are selected :
Capasity : 7,49 GB
Filsystem : FAT32 (Standard)
Allocation size : 32 kilobyte
Volume name : (blank)
Fast formatting (box not ticked)
Pushing START
Formatting warning, and OK (takes 12 min on my computer)
3) Finally my card is really formatted, and ready to use.
4) Now I copies the files to the card. (See order above)
I still get the same error message on the CPC :-[
What do I do wrong ? ? ?
Looking forward for any suggestions.
Yours
Terje Grind
Norway
Hello,
I am not sure about it, but I think that's not a good idea to let the firmware update on the card. Did you setup too the drive as A: or B: ?
I myself experienced tonight something weird, I wanted to test the new No Recess' frontend. But, after loading the Hxc program, error 64 (and the card is blocked). Damn No Recess, another bugged software :-). So I decided to use again the old frontend : same result.
I have been obliged to setup the Hcx Sdcard reader as A: drive ("jumpering" and removing the internal 3 inches drive :-( ) : result, everything is fine, even with the last frontend update.
I haved setuped (uh, does not sound like an english expression) again the Hxc card as B: drive and putted back the internal drive : everything is still ok !!
T&J/GPA
Hi :)
My setup is as simple as it can get.
1) Plain CPC6128, without any add ons or anything else.
2) HxC SD Card connected as Drive B: . . . .
. . | .
. . | .
3) Using Floppy lead, and power lead from Urban Retro.
4) Everything works perfect with my "1GB Kingston SD Elite Pro" card
With my "8GB Transcend SDHC Class 10" it used to work a few weeks AGO, but just not NOW.
YES, the update file is also on my KINGSTON card.
Just a wild theory, could it have something to do with the BOOTLOADER released a few weeks ago ? ? ?
Yours
Terje Grind
Norway
Hi guys,
Can't help on that one, the software is not involved here.
Let's wait for Jeff's answer! 8)
Quote from: norecess on 05:14, 23 August 10
4) I still enjoy watching turn-disc parts. :)
Good point ;)
Quote from: Terje_Norway on 17:50, 23 August 10
Hi 8)
I'm having problem formatting the SD cards. A few weeks ago I bought 3 x "Transcend SDHC 8GB Class (10)", and up to recently these THREE cards has been working perfectly.
I did the updates that came this weekend. I used a "1GB Kingston SD elite pro" card for the updates, and that works. The HxC hardware is now updated to the last firmware (1.3.0.0).
So I decided to reformat one of the Transcend cards, and put everything on a fresh card.
I formatted it using "SD Formatter V2.9.0.5", and then formatted it in windows. The I copied the files on the card in the following order :
1) HXCFE_V1_3_0_0.UPD
2) HXCSDFE.CFG
3) AUTOBOOT.HFE
4) plus a lot of HFE files
On my CPC I get the following message "Reading FAT". That message stays on all the time. So I tried another solution. With the UPD file on the card I tried to update the firmware from the card. Result is the LED blinks 4 times, then a pause and four new blinks. That means it can't find and UPD on the card, and that it can't read the card.
Obviously there is something wrong with the formatting of the card.
So how have I formatted the card (This is going to be detailed, as to find out what I do wrong)
1) Within "SDFormatter V2.9.0.5" I have the following settings for my "Transcend SDHC 8GB Class 10" card :
Format type - "FULL (Erase ON)"
Format Size adjustment - "OFF"
Then "Format" and "OK" (takes 16 min on my computer)
When the format is finished I get the following information:
Volume Information
-File system : FAT32
-Total space = 7.48 GB(8,040,480,768 Bytes)
-Cluster size=32768 Bytes
2) Then I goes to Windows Explorer to format the card :
The following options are selected :
Capasity : 7,49 GB
Filsystem : FAT32 (Standard)
Allocation size : 32 kilobyte
Volume name : (blank)
Fast formatting (box not ticked)
Pushing START
Formatting warning, and OK (takes 12 min on my computer)
3) Finally my card is really formatted, and ready to use.
4) Now I copies the files to the card. (See order above)
I still get the same error message on the CPC :-[
What do I do wrong ? ? ?
Looking forward for any suggestions.
Yours
Terje Grind
Norway
mhhh 12 minutes of formatting seems very long to me...
anyway can you try to go back to an older firmware ? :
http://hxc2001.free.fr/floppy_drive_emulator/oldfirmware.zip
what was your previous firmware version ? (when the cards works...)
Hi Jeff,
On my three years old PC everything goes slow, so 12 min to format a card is slow, but I have become used to it :(
As for older firmware I have checked with another piece of hardware. I had the biggest order according to Lotharek when I bought 10 units, so I still have 8 unused units. One is used for a CPC6128 and the other is used on a Amiga 500. I did raid an computer museum years ago ! ! ! YES I'm probably "crazy", but I'm sure I have more computers than most of You out there. All in all I have about 60-70 retro computers (I think), including about 20 Amstrad machines. 8)
The next piece of hardware I tested with my Transcend card has :
Firmware V1.1.0.1 (As it was originally shipped with) gave the a new error "rderr=00000000 2". That indicates that the error must be related to the card.
I also tested this firmware with my working KINGSTON card, and that worked almost perfect ! ! !.
Trying to run "HXC" (V2.0) from the card gave me the following error on screen (CPC screen that is ;) )
HxC card is configured as Drive B:
With disc in Drive A: I get an "ERROR: Floppy Access Error! [64]" on screen
"Direct access LBA:00000000" on LCD
Without disc in drive A : I get an "ERROR: Floppy Access Error ! [68]" on screen, nothing on LCD
Swapping hardware, and it worked like a dream. HXC program worked like it should.
So what is the conclusion.
The "HXC V2.0" doesn't work on old firmware. Could it be related to the updated BOOTLOADER ? ? ?
Have to investigate further tomorrow.
Yours
Terje Grind
Norway
Quote from: Terje_Norway on 00:35, 24 August 10
Hi Jeff,
On my three years old PC everything goes slow, so 12 min to format a card is slow, but I have become used to it :(
As for older firmware I have checked with another piece of hardware. I had the biggest order according to Lotharek when I bought 10 units, so I still have 8 unused units. One is used for a CPC6128 and the other is used on a Amiga 500. I did raid an computer museum years ago ! ! ! YES I'm probably "crazy", but I'm sure I have more computers than most of You out there. All in all I have about 60-70 retro computers (I think), including about 20 Amstrad machines. 8)
The next piece of hardware I tested with my Transcend card has :
Firmware V1.1.0.1 (As it was originally shipped with) gave the a new error "rderr=00000000 2". That indicates that the error must be related to the card.
I also tested this firmware with my working KINGSTON card, and that worked almost perfect ! ! !.
Trying to run "HXC" (V2.0) from the card gave me the following error on screen (CPC screen that is ;) )
HxC card is configured as Drive B:
With disc in Drive A: I get an "ERROR: Floppy Access Error! [64]" on screen
"Direct access LBA:00000000" on LCD
Without disc in drive A : I get an "ERROR: Floppy Access Error ! [68]" on screen, nothing on LCD
Swapping hardware, and it worked like a dream. HXC program worked like it should.
So what is the conclusion.
The "HXC V2.0" doesn't work on old firmware. Could it be related to the updated BOOTLOADER ? ? ?
Have to investigate further tomorrow.
Yours
Terje Grind
Norway
No this firmware is too old (mhh i don't have this version in the release notes!!! are you sure it's 1.1.0.1 ?) for the file manager (some bug have been corrected since).
And the bootloader is only used during firmware update. so it's not the problem.
Can you try the 1.2.0.0 ?
if this doesn't work , can you dump the full sdcard, pack the 8 GB file image (should be small at the end) and send it to me ? i need this to understand what happens
A bit off-topic, but:
Quote from: Terje_Norway on 20:54, 23 August 10
3) Using Floppy lead, and power lead from Urban Retro.
what power lead do they offer?
Hi,
A few updates on the SD card formatting problem.
Quote from: Gryzor on 06:29, 24 August 10
A bit off-topic, but:
what power lead do they offer?
"Amstrad CPC power cable for SD HxC floppy disk drive"
http://cgi.ebay.co.uk/Amstrad-CPC-power-cable-SD-HxC-floppy-disk-drive-/230508124304?pt=UK_VintageComputing_RL
Up for auction is a 1m long power cable for use with the SD HxC floppy emulator card.
By using this cable, power to the card is supplied directly via the Amstrad CPC monitor (or via any other external PSU that can plug to and power up the Amstrad CPC keyboard).
Quote from: Jeff_HxC2001 on 06:11, 24 August 10
No this firmware is too old (mhh i don't have this version in the release notes!!! are you sure it's 1.1.0.1 ?) for the file manager (some bug have been corrected since).
And the bootloader is only used during firmware update. so it's not the problem.
Can you try the 1.2.0.0 ?
if this doesn't work , can you dump the full sdcard, pack the 8 GB file image (should be small at the end) and send it to me ? i need this to understand what happens
Yes, firmware is
v1.1.0.1. This firmware is old, and I haven't been able to find any references for it ! ! !. Besides, it is the firmware that was on my test unit, nothing more.
The last firmware that worked with my Transcend card
could have been v1.1.3.0. I can't remember using these three cards with
v1.2.0.0. and above.
So Jeff, let us start eliminating errors.
1.) Could it be something wrong with my formatting procedure described a few postings ago ? ? ?.
2.) Can't completely forget about the error message I get using the Transcend cards with firmware
V1.1.0.1 ("rderr=00000000 2"). What does this error indicate ? ? ?
3.) With firmware
v1.3.0.0 the "error" I get is "Reading FAT..". Is it related to point
2.) Together these two different errors indicates that the problem lies with the Transcend card.
That kind of problems could usually be solved with formatting the card ! ! Now we're back to start.
I'll update the second unit to firmware
V1.1.3.0 and see if that makes any difference.
I'll be back when it is done.
Yours
Terje Grind
Norway
I'm glad having none of these problems. My interface isn't updated yet and it works out of the box!
Thanx to jeff for releasing HxC Manager 2.0 - you did a great job!
Hi (again) ;)
Now I have done a lot of updates to the firmware on my "second Amstrad" unit :
Firmware V1.1.3.0 : The three Transcend cards gives "Reading FAT.."
Bootloader V1.0TOV1.1 : Works perfect
Firmware V1.2.0.0 : The three Transcend cards gives "Reading FAT.."
Firmware V1.2.0.1 : The three Transcend cards gives "Reading FAT.."
Firmware V1.3.0.0 : The three Transcend cards gives "Reading FAT.."
Have also made an attempt to "downgrade" back to firmware V1.2.0.1 that gives FOUR blinks than a pause and FOUR new blinks (Means UPD file not found on SD card). Have reset my CPC and inserted the card, now it can't find "Hxcsdfe.cfg" on SD card (file is not on the KINGSTON card) That means that it is nothing wrong with the KINGSTON card.
After all the updates, I have discovered something ODD.
BOOTLOADER enclosed with firmware V1.2.0.0 is dated 07.08.10 13:01 - size 9216 bytes
BOOTLOADER enclosed with firmware V1.2.0.1 is dated 07.08.10 13:01 - size 9216 bytes
BOOTLOADER enclosed with firmware V1.3.0.0 is dated 11.08.10 20:46 - size 9728 bytes
What is the difference between these TWO bootloaders ? ? ?
I have compared the two files, and there seems to be a lot of differences (at least when the two files are compared to each other)
Looking forward to hearing from You Jeff ;)
Yours
Terje Grind
Norway
Quote from: Terje_Norway on 15:51, 24 August 10
Hi (again)
Now I have done a lot of updates to the firmware on my "second Amstrad" unit :
Firmware V1.1.3.0 : The three Transcend cards gives "Reading FAT.."
Bootloader V1.0TOV1.1 : Works perfect
Firmware V1.2.0.0 : The three Transcend cards gives "Reading FAT.."
Firmware V1.2.0.1 : The three Transcend cards gives "Reading FAT.."
Firmware V1.3.0.0 : The three Transcend cards gives "Reading FAT.."
Have also made an attempt to "downgrade" back to firmware V1.2.0.1 that gives FOUR blinks than a pause and FOUR new blinks (Means UPD file not found on SD card). Have reset my CPC and inserted the card, now it can't find "Hxcsdfe.cfg" on SD card (file is not on the KINGSTON card) That means that it is nothing wrong with the KINGSTON card.
After all the updates, I have discovered something ODD.
BOOTLOADER enclosed with firmware V1.2.0.0 is dated 07.08.10 13:01 - size 9216 bytes
BOOTLOADER enclosed with firmware V1.2.0.1 is dated 07.08.10 13:01 - size 9216 bytes
BOOTLOADER enclosed with firmware V1.3.0.0 is dated 11.08.10 20:46 - size 9728 bytes
What is the difference between these TWO bootloaders ? ? ?
I have compared the two files, and there seems to be a lot of differences (at least when the two files are compared to each other)
Looking forward to hearing from You Jeff
Yours
Terje Grind
Norway
Firmware/bootloader files are scrambled. so don't try to compare them
For the sdcard problem what i see is that your transcend card didn't work at all (this not a firmware/bootloader version problem...).
Unfortunately i can't help you without one them here.
Last thing : Can you dump the one you are using for the tests please ?
Hi Jeff 8)
Thanks for Your fast reply.
I'll do more research concerning the Transcend cards, and if I can't get it working I'll send one of the Transcend cards to You. ;D
BUT concerning the BOOTLOADER files. Are all three files the same ? ? ?
I have compared the bootloader file within firmware V1.2.0.0 with V1.2.0.1 (These bootloader files are identical ! ! )
Compared with bootloader within firmware V1.3.0.0 (The two files are not identical) Both date and size is different.
To me it could be a identification of TWO different files ? ? ?
Have You found anything wrong with my formatting procedure ? ? ?
Yours
Terje Grind
Norway
Quote from: Gryzor on 19:01, 10 August 10
Thanks for all the support mate... it's much, much appreciated.
I never remove a card while the board is still on. And I don't turn it off while it's obviously reading or writing something -but then again, I'm not sure what 'obviously' means here.
About the file method you suggested: this is all done on the PC, right? But what will it achieve?
Also, thanks about the LBA clarification. I hadn't seen it with older firmware versions, and I did guess that it probably didn't mean anything was wrong, but thought I'd ask.
Shame, I'd like some yellow and green blinkies... :D
Off to a date now, already running late. See what your board does? Kills social life!
Ok i got your Sdcard Gryzor : The problem is that you have formatted this sdcard in FAT (16) and not in FAT32.
As said in the user manual the floppy emulator is FAT32 based.
So after a simple fat32 formatting all is working well...
Quote from: Terje_Norway on 17:21, 24 August 10
Hi Jeff 8)
Thanks for Your fast reply.
I'll do more research concerning the Transcend cards, and if I can't get it working I'll send one of the Transcend cards to You. ;D
BUT concerning the BOOTLOADER files. Are all three files the same ? ? ?
I have compared the bootloader file within firmware V1.2.0.0 with V1.2.0.1 (These bootloader files are identical ! ! )
Compared with bootloader within firmware V1.3.0.0 (The two files are not identical) Both date and size is different.
To me it could be a identification of TWO different files ? ? ?
Have You found anything wrong with my formatting procedure ? ? ?
Yours
Terje Grind
Norway
Please use this tool to dump your sdcard :
http://www.alexpage.de/download/usbit/usbit.zip (http://www.alexpage.de/download/usbit/usbit.zip)
(use the "Device Mode")
After this compress the file image (in rar for example) and send me the archive.
Thanks by advance.
Quote from: Jeff_HxC2001 on 20:27, 24 August 10
Ok i got your Sdcard Gryzor : The problem is that you have formatted this sdcard in FAT (16) and not in FAT32.
As said in the user manual the floppy emulator is FAT32 based.
So after a simple fat32 formatting all is working well...
Erm... I don't have a hat to eat, but even if I did format it as FAT16 before I sent it , I'm 100% sure that at *least* one of the times I formatted it was in FAT32 :D I think FAT32 is the default anyway?
I'll try to find the other SD cars that presented the same problem...
Thanks for letting me know :)
@Terje: uh.... thanks for the power cable info, I had already bought this one :D I just didn't remember it was that seller!
Quote from: Gryzor on 10:43, 25 August 10
Erm... I don't have a hat to eat, but even if I did format it as FAT16 before I sent it , I'm 100% sure that at *least* one of the times I formatted it was in FAT32 :D I think FAT32 is the default anyway?
I'll try to find the other SD cars that presented the same problem...
Thanks for letting me know :)
@Terje: uh.... thanks for the power cable info, I had already bought this one :D I just didn't remember it was that seller!
Yes but the card i received was in FAT16... and this card doesn't present any problem (once in fat32).
and no, for a 2GB card the default file system is FAT16...
So, finally... 1 week after latest release... is everyone happy with latest Manager ?
Quote from: norecess on 19:06, 30 August 10
So, finally... 1 week after latest release... is everyone happy with latest Manager ?
I already wrote which additional feature I would like to have. :P
Apart from that it is really good and working absolutely flawless so far. 8) :)
Quote from: norecess on 19:06, 30 August 10
So, finally... 1 week after latest release... is everyone happy with latest Manager ?
Hi there,
yep, I'm pretty happy with it: my primary method of using it is via the push button and LCD screen, but can report (finally) the reason why I couldn't get the Floppy Manager working with my particular setup that I was writing about earlier in this forum thread: it was due to the multiple
ABBA Drive Select switch mods that I have installed on my
CPC6128. regardless of whether the SD HxC was set to DS0, 1, 2 or 3 or set to A (1st) drive or B (2nd) drive - the floppy manager would return an error code (refer to my earlier post for the scenarios that would generate them).
fortunately, I have an
unmodified CPC6128 on hand, and could confirm that the Floppy Manager software was working properly with the SD HxC (updated to latest
firmware v1.3.13.0) when set as the
B drive via the jumper settings for
Drive Select 1, and to also try out the ROM version of the Floppy Manager programmed on to my Symbiface II... works quite well, and it's quicker to operate than the Floppy Manager that loads from Autoboot.hfe
so, my request (or comment) for help would be this: any chance you could install this external floppy mod on to your 6128, and figure out why this ABBA drive mod appears to be causing all the program error codes???
I've attached a screen shot from Amstrad Technical Manual #3 of a schematic for the mod that should expand on what I'm talking about ;-)
the screenshot describes ABBA switches for DS0, 1, 2 and internal 3" floppy and how they're soldered to various points on the circuit board..
cheers!
Will this HxC work on a 6128 Plus??? Any pitfalls, and how difficult would it be to get it up and running???
Yep, I've got mine attached to my 6128+. I'm using the external cable at the moment, though I've removed the internal drive and made an adapter cable to take the power from the internal drive feed. I might look into making a suitable internal cable for the data at some point, then mounting it entirely internally but what I have now is working ok for the time being.
Yes, working with any CPCs (software and hardware, including 64Kb machines).
Any new firmware/software/manager versions while I was getting married? :)
Just for the record: My HxC SD-Interface is running just fine as drive 0 via ABBA switch.
thanks to eliot and the cpc parts web site, I got some much needed parts for my internal CPC6128 cable to HxC device. I now have the 3" drive replaced with the HxC device. I can use Drive A, no problems. I can use the Boot Loader Manager and insert .HFE discs, no problems. In fact, all is good and I'm very happy with the device and the usage. I can even have my SF2 connected and use lots of ROMs too.
...but..(and there is always a but)... I still cannot figure out how to get the HxC device to show me Drive B (I've inserted a .HFE image into Drive B, rebooted and when I do |b:cat, I just see the content of Drive A).
The jumper is set to:
[ ][ ][ ][ ]
[.][ ][ ][ ]
[.][ ][ ][ ]
which should tell the device that it is Drive A. If anyone knows how I can overcome this "minor" niggle, I'd really appreciate it!
As I made a custom internal cable to go from the 26pin to 34pin connector, can someone tell me what cables (pin#) I need to cut and connect to a switch to make an ABBA switch? (I took a look at the wiki article but maybe I'm being thick ??? but I cannot figure out what cable/pin# I'm meant to attach the switch too)
UPDATE: After receiving a new HxC SDCard device today, I did a FAT32 format (not quick format) on a new Transend 2Gb card, put the HXC20.ROM into the SF2 card. ran |HXC and wow! I'd not seen the new version of the Manager - it is truly great!
I understand the Slot concept now. I can get 10 DSK/HFE discs, one into each slot and then by pressing the right button, I can swap out the DSK/HFE disc for the next one in the queue (same as removing a real disc and putting in a new one). This is totally awesome! and removes any need for me to faff about trying to do stuff with Drive B. Maybe I just didn't get the Slot concept or my old HxC SDCard wasn't at the latest version or something. Am a very happy customer now...... time to get converting all my DSK files to HFE now....
Glad the manager works as a charm on your side :)
Hi
A good few months ago I posted asking what I could do with my 464+ , if could add a floppy or a flash interface etc. At the time I got some great replies but the gist was - add floppy interface if got the parts and skills ( but still no rom) add a DDI-1, regret it only having 64k etc
Well now I have one of lothareks sd card HxC's for an atari, and as luck would have it i now have a chance to swap / get me a DDI-1 from a friend !
My questions are then, please-
A could I boot all/most games from the HxC via attached DDI?
b is the memory on the 464+ going to be a problem , is all going to work smoothly
C would I have any problems with drive numbers with the above?
D or still best to get a 6128.. Or investigate if adding an internal floppy Interface etc was viable
Ta for help guys! Im getting there:)
The difficulty is getting the parts, do you have the information necessary to install the upgrades?, the disk rom is already in the cartridge.
You need to confirm that the ddi-1 will plug into your 464+ I do not know if the two roms will clash, I think the ddi rom will override the cartridge rom.
The PCB is designed for 128KB ram so if you can get the parts you can upgrade to 128K.
Hi
The friend actually doesn't yet know if it's a DDI-1 or an FD1(?). I should hear soon.
All I presently have is the 464plus and a burnin rubber/ basic cart. Is that what you mean has this 'rom' I heard about ? See, I don't know if that's an extra dos or, well anything sorry.
Sorry neither do I have details of parts needed for adding on motherboard floppy interface or more ram so if anyone could post those (or please pm me) as well as my other questions.. Well that'd be ace!
Thanks for your reply!:)
Actually, all 64Kb machines are compatible ! I took special care in not using the 6128's banks for the manager. Regarding the HxC Floppy Emulator itself, it's absolutely not related to memory.
The key component in determining whether you can add a disk controller to the 464+ is the SED 9420 data separator, I do not know where to get this from or even if it is possible to get one at all, if you cannot find one of these you cannot upgrade your machine to disk.
It would probably be simpler and cheaper to buy a CPC6128.
I have a 464+ but because I cannot find a data separator I have just bought a 6128+, probably for less than the disk upgrade components would have cost me.
Yes the basic cartridge contains the "firmware" of the machine including disk control functions.
Whether it is a ddi-1 or fd-1 does not matter, get it if you can since the fd-1 which is included with a ddi-1 can be used as a second drive attached to your 6128 if you get one, although if you get an hxc sd interface you won't need a second drive.
Nobody mentioned that there has been a new release for both the PC software and the firmware (though of little interest to CPC users):
Software:
Quote
04/09/2010: HxCFloppyEmulator 1.3.14.0
-> New file Support : Prophet IMG File format.
-> ST/MSA : Track skew corrected.
-> ST : Disk geometry detection corrected/enhanced : All ST files should work now.
-> GUI: Settings and last used path are now saved.
-> "Load RAW Image" : New "Skew" parameter.
-> HFE file Writer : Speed up while writing to a sdcard.
-> IPF : CAPSImg.dll removed to be in conformance with the SPS license.
Firmware:
Quote
05/09/2010: Firmware SD HxCFloppyEmulator v1.3.0.2
- Shugart & PC interface mode behavior corrected.
Quote from: steve on 02:15, 16 September 10The key component in determining whether you can add a disk controller to the 464+ is the SED 9420 data separator, I do not know where to get this from or even if it is possible to get one at all, if you cannot find one of these you cannot upgrade your machine to disk.
At http://aleasoft.iespana.es/sinclair/dostotres.html (http://aleasoft.iespana.es/sinclair/dostotres.html), this guy mounts 4 TTL chips instead SED for a Spectrum +3, perhaps the same could be adapted to CPC+ 464
thanks guys, I'll look at getting that interface or find a 6128.
soldering that level is beyond me I think..
ta:)
Get a 6128! ;)
Rev C SD HxC Floppy Emulator preorders are now open on ebay ! :
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=180575793600
Is there a list of changes somewhere, for the Rev.C?
New firmware v1.3.0.4
What does double step support mean?
Double Step normaly applies to 5.25" drives and means that when using a 360kb disk in a 1.2Mb drive that the head of the drive must be moved twice per track to properly position it on the disc surface because of the differences in the head between low density and high density drives.
did someone recieve the new HxC Rev. C. I payed in Okctober and I didn`t get one till today!?!
xesrjb
Not yet, and I already sold my Rev B board to a friend... >:(
Quote from: robcfg on 10:46, 26 November 10
Not yet, and I already sold my Rev B board to a friend... >:(
Don't worry, boards are incoming :
http://torlus.com/floppy/forum/viewtopic.php?t=442&postdays=0&postorder=asc&start=15
Thanks for the info!
The sd floppy emulator is top notch stuff!
Uff, I got it!!!
xesrjb
a small news:
New Rev C SD HxC Floppy Emulator Preorder :
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=180592972686 (http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=180592972686)
and a new webstore is now open :
http://www.lotharek.pl/ (http://www.lotharek.pl/)
http://lotharek.pl/null/product/info/3 (http://lotharek.pl/null/product/info/3)
Project webpage :
http://hxc2001.free.fr/floppy_drive_emulator (http://hxc2001.free.fr/floppy_drive_emulator)
Mine just arrived!
Can't wait to try it at home...
Thank you, Jeff!
Ah... you're in for a treat then!
Can't wait to receive mine (my second HxC :)) :P
Quote from: norecess on 14:36, 01 December 10
Can't wait to receive mine (my second HxC :)) :P
No treat for you, then :D
I'd be buying a second unit myself if I could afford it...
Quote from: Jeff_HxC2001 on 22:10, 17 October 10
Rev C SD HxC Floppy Emulator preorders are now open on ebay ! :
http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=180575793600 (http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=180575793600)
Thanks again, my two units have arrived in Munich. I had a look at them via Webcam: They are really very proffessionaly produced. I'm looking forward to use your excellent product quite soon.
btw.: Is there a possibility to jumper them as drives C and D on the CPC? Anybody ever tried?
Now, I checked how it runs! Great :) :) .
xesrjb
Do you know Total Commander for DOS/Windows?
Well, you do... Surfing the web I found out that some spanish guys are working on a Total Commander for VDrive.
This would be a great tool for hxc floppy, too ;)
http://picasaweb.google.com/dadcezgs/AmstradCPC# (http://picasaweb.google.com/dadcezgs/AmstradCPC#)
(http://lh3.ggpht.com/_u2camLVKn_E/TKdhHo-VEQI/AAAAAAAAAIM/Le1h1vv_oA0/vcommander_vdrive.png)
Ooooh sweet.... and I can wholeheartedly agree with the HxC comment!!!!!
But what is the VDrive?
VDrive is a home brewn project similar to the HxC one (as far as I know...)
http://www.octoate.de/wp/2009/03/27/vinculum-vdrive-connected-to-the-cpc/
Surfing the web I found out that some spanish guys are working on a Total Commander for VDrive.
I ** LOVE ** this UI. Makes me think about HxC software..
And they're actually porting TC to that? Awesome...
HxC Manager is good - Total Commando would be great ;D
So - where're the good cpc coders?
Quote from: CPCIak on 11:49, 23 December 10
HxC Manager is good - Total Commando would be great ;D
So - where're the good cpc coders?
It's all open source, you can contribute in which way ever you like. Look at the HxC homepage.
Quote from: TFM/FS on 22:16, 05 January 11
It's all open source, you can contribute in which way ever you like. Look at the HxC homepage.
mhh you want Total Commander on cpc to do what? and what is the point with the hxc ?
If you want copy 2MB files through the floppy interface this sound to me a bad idea ;-)
It would make copying/uploading files much easier - just drag & drop ;)
No need for tools like Discology or XEXOR
important firmware update ! :
http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_firmware.zip
http://hxc2001.free.fr/floppy_drive_emulator/sd_hxc_floppy_emulator_firmware_release_notes.txt
http://hxc2001.free.fr/floppy_drive_emulator/index.html#download
Quote
25/01/2011: Firmware SD HxCFloppyEmulator v1.5.0.0
- SDcard : Init frequency corrected
- SDcard : Multi sector read & Write access added.
-> SDCard access time improved (Slow sdcard issues corrected)
- Some important parts of the floppy write support fully rewritten : Important codes improvement (speed & size)
-> MFM ISO Sector write support speed & code size improvement.
-> Amiga write support speed & code size improvement .
General result: Faster write data throughput.
- New MFM/DD write support bitrate added.
-> 300kbits/s (256/512/1024 bytes sectors).
- FM write support added.
-> 128bytes sector SD/FM write support added.
-> 256bytes sector SD/FM write support added.
-> 512bytes sector SD/FM write support added.
-> 1024bytes sector SD/FM write support added.
-> SD/FM write support bitrate : 250kbits/s, 300kbits/s & 500kbits/s
- E-mu write support added (E-mu emulator, E-mu emulator II,...)
Note : Need the Rev C SD HxC Floppy Emulator hardware!
-> 3584bytes sector FM E-emu write support added.
-> E-mu write support bitrate : 312kbits/s
A big Thanks to Kris VC / esynthesist (http://www.emxp.net/) for all tests done on this firwmare
with the E-mu Emulator & E-mu Emulator II.
Without this great help, releasing this new feature wouldn't be possible.
- Two floppy drive emulation improvement/bug corrected
-> The two virtual floppy disk drive can have different bitrate now.
(example : an 1.44MB floppy disk in the first disk drive and a 720KB in the second disk drive.)
- SDCard HxC Floppy emulator settings (sound/blacklight...) are now stored into the eeprom
and used at power up. At power up the last known settings are used.
Ahhhh about time we had something to fiddle with!! Will try it next week, even though it won't do much difference for me :)
Thanks for the update Jeff!!! ;D
Edit:
In the Handbook you write:
"Note 3: If you are using the external floppy port of an Amstrad CPC6128 computer, you
must connect the floppy cable on the opposite side to the emulator (red wire to the left).
... . "
It this true for the CPC Plus only or for the CPC6128 ??? I think it's true only for the Plus, but I may be wrong (can't acces my docs from this laptop, but I have something like this in my memories).
Quote from: TFM/FS on 20:37, 27 January 11
Thanks for the update Jeff!!! ;D
Edit:
In the Handbook you write:
"Note 3: If you are using the external floppy port of an Amstrad CPC6128 computer, you
must connect the floppy cable on the opposite side to the emulator (red wire to the left).
... . "
It this true for the CPC Plus only or for the CPC6128 ??? I think it's true only for the Plus, but I may be wrong (can't acces my docs from this laptop, but I have something like this in my memories).
I have only a CPC6128 here. for the + this is another connector (centronic)?
Quote from: Jeff_HxC2001 on 21:01, 27 January 11
I have only a CPC6128 here. for the + this is another connector (centronic)?
Well, let me speak for the German CPCs first. Both the 6128 and CPC Plus have a centronics connector. But the Plus has another pin-out. This means in a flat cable the wires are shiftet by 1 (sorry can't explain it better in English).
The GB 6128 has (like I know) a panel-connector, I don't know the pin out there now.
However:
- CPC6128 and CPC Plus have a different pin-out.
- And like I thought, the CPC6128 is shuggart compatible.
Well, I have to get my docs an look at it... if somebody else has a comment, feel cordially invited to post :)
The red wire on the CPC is always on the same side (righthand side looking at the rear of the CPC). The difference between the standard CPC and the plus is that the flat cable is shifted one place to the right on the plus (ie: Red isn't connected at all, wire two goes to the right most terminal) and on the standard CPC the cable is shifted two places to the left (ie: The red wire is connected to terminal 3).
I've made a connection cable with two centronics plugs, one for standard one for plus for my HxC, works fine, I'll post a picture of it if anyone is interested.
Bryce.
Quote from: Bryce on 23:51, 27 January 11
The red wire on the CPC is always on the same side (righthand side looking at the rear of the CPC). The difference between the standard CPC and the plus is that the flat cable is shifted one place to the right on the plus (ie: Red isn't connected at all, wire two goes to the right most terminal) and on the standard CPC the cable is shifted two places to the left (ie: The red wire is connected to terminal 3).
I've made a connection cable with two centronics plugs, one for standard one for plus for my HxC, works fine, I'll post a picture of it if anyone is interested.
Bryce.
Perhaps it's better to have only 1 centronics plug on your cable and an additional cable only for your CPC plus. So, you can't plug in the wrong centronics plug in your CPC plus (it's deadly for the internal 3" drive)!!!
xesrjb
I took the easier option and just wrote "Plus" on one of them :) That saved me buying an extra Centronics connector :)
Bryce.
First I'd like to thank Jeff for this major update.
Since I've got my HxC Floppy I've asked lotharek several times if there'll ever be a case available. Unfortunately he never answered.
Well, so I've made my own case. Cool, isn't it :D
(http://lh6.ggpht.com/_h9x-AgD8xDA/TUU1g_VdBiI/AAAAAAAAA0A/qsBlxaph4I4/s400/HxC%20Geh%C3%A4use.JPG) (http://picasaweb.google.com/lh/photo/iPOg4yIhfj3XhB5-s-_1sg?feat=embedwebsite)
Cute and simple... :) What did you use?
manufacturer: Strapubox 124x72x30mm
Conrad Electronics order number: 528373-62
price: 2,35€
Great work, but maybe you should use an own PSU for it. (Depends on "how much" you've connected to the Expansion port).
I know "power stealing" from the monitor is probematic. If the HxC is the only device connected, everything works great.
The 5V supply has tonnes of headroom (not a reference to my icon), you can easily supply the HxC and a few peripherals without any problems. My 6128 is connected to an MP2 not a monitor, but it has a similar output and I have connected the HxC, MegaROM, PS/2 Mouse, DKT speech synth and DKT lightpen all at once without any problems, in fact I still had around 80mA left over :) On the Plus (due to the disc drive motors being powered from the 5V too) you might start having problems when the drive is running.
Bryce.
Hey guys/Jeff,
On a MicroSD that was working perfectly (used it today) I added Batman FOrever and SubHunter and now I get (when the interface loads) Floppy Access Error! [64] . I had asked this half a year ago, but I got no reply... any help? Window's ScanDisk (or whatever nowadays) reports no problems...
Cheers
Themis
Hmmm weird. I deleted the specific files from the SD, then copied them again, and the SD seems to be working fine.
However: the one-disk version of Batman Forever doesn't load (can't find disk in drive, maybe HxC's limitation??). BUT! The HXC converter cannot convert the single-sided version of the demo...
Can anyone confirm?
Jeff, if you can test the attached file which causes HxCFloppyEmulator 1.5.2.1 to freeze (or crashes, depending on its mood), I'd be grateful...
Debug info:
Problem Event Name: APPCRASH
Application Name: HxCFloppyEmulator.exe
Application Version: 1.5.2.1
Application Timestamp: 4d3ae63c
Fault Module Name: HxCFloppyEmulator.exe
Fault Module Version: 1.5.2.1
Fault Module Timestamp: 4d3ae63c
Exception Code: c0000005
Exception Offset: 000056cd
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1032
Additional Information 1: cb19
Additional Information 2: cb1977b9167d9009e8c446802ebdbca0
Additional Information 3: 844f
Additional Information 4: 844f45d7f6cea0c52e79411ff9bb9b67
PS I just noticed FTDI D2XX Direct Drivers on the download page. What is this for?
I ran Batman Forever (single disk version) from the HxC on a 4GB SD Card and it worked fine, are you using the latest version of the converter?
Bryce.
Yes, 1.5.2.1 . Could you upload the hfe?
I'll send you it tonight.
Bryce.
Cheers mate!
Quote from: Gryzor on 11:53, 29 March 11
Hey guys/Jeff,
On a MicroSD that was working perfectly (used it today) I added Batman FOrever and SubHunter and now I get (when the interface loads) Floppy Access Error! [64] . I had asked this half a year ago, but I got no reply... any help? Window's ScanDisk (or whatever nowadays) reports no problems...
Cheers
Themis
Not sure but your random sdcard problems is maybe due to a compatibility problem between your SDcard and the Revision B board.
To correct this, you can put a 1800 ohms (1.8Kohms) resistor in parrallel of R28 (between pin 1 & 2 of U11 for example).
Schematic : http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_Kit.zip (http://hxc2001.free.fr/floppy_drive_emulator/SDCard_HxCFloppyEmulator_Kit.zip)
This possible issue is corrected with the rev C boards.
For the batman demo the single sided disk seems to be wrong (bad track numbers...). Not sure what i should do in this case.
The one disk version is working well.
Another point : Your issues can be due to a floppy cable problem...
Last point : did you have the last firmware version?
EDIT : And very important : Can you check you power supply?
Quote from: Gryzor on 12:03, 29 March 11
However: the one-disk version of Batman Forever doesn't load (can't find disk in drive, maybe HxC's limitation??).
The file you attached here is side A from disk 1. You also need side B and disk 2
Hey Jeff,
Thanks for your really prompt reply...
As it so happens, while you were typing this I was updating my FW (hadn't done so in a while). Guess what - it worked first time :)
As for the single-sided version, I think in another thread it was pointed out that there was something weird with track numbering indeed (yet it runs under emulators).
All's well then - no need for soldering perhaps. But could you expand on what this would fix?
Thanks again!
T
PS @Markus: duh :D Of course, but the problem lies with the converter not converting the disk, that's why I only attached that one :)
Hi Jeff,
a technical question: I assume that adding the extra resistor is to slightly rise the 3.3V line voltage? How high are you rising it? Are there issues with certain SD cards that need to be slightly above 3.3V? Or were you slightly below the 3.3 volts on Rev B. ?
Bryce.
Quote from: Bryce on 12:39, 29 March 11
Hi Jeff,
a technical question: I assume that adding the extra resistor is to slightly rise the 3.3V line voltage? How high are you rising it? Are there issues with certain SD cards that need to be slightly above 3.3V? Or were you slightly below the 3.3 volts on Rev B. ?
Bryce.
This resistor push the sdcard voltage up to 3.55V. This reduce the PIC/Voltage difference.
According to the SDCard specification ALL SDCard must support up to 3.6V.
Ah ok, interesting. I haven't experienced this problem with my device, but if I do I'll swap the resistor (not as messy as adding a parallel resistor).
Thanks,
Bryce.
Quote from: Gryzor on 12:30, 29 March 11
As for the single-sided version, I think in another thread it was pointed out that there was something weird with track numbering indeed (yet it runs under emulators).
Where ?
Quote from: Gryzor on 12:30, 29 March 11
All's well then - no need for soldering perhaps. But could you expand on what this would fix?
If you have no strange sdcard behaviors (sdcard not detected when the system is cold or warm...) no.
The issue is possible with Rev B boards when the power supply is over 5.3V and/or with some sdcard.
Quote from: Bryce on 12:55, 29 March 11
Ah ok, interesting. I haven't experienced this problem with my device, but if I do I'll swap the resistor (not as messy as adding a parallel resistor).
Thanks,
Bryce.
In this case the value of the new resistor is not the same !!! And you must change another one too:
R28 must be changed to 180 ohms and R30 must be changed to 330 ohms.
R28=180ohms (old value 220 ohms)
R30=330ohms (old value 360 ohms)
OR
You can put a 1800 ohms (1.8Kohms) resistor in parrallel of R28 (between pin 1 & 2 of U11 for example)
As you want ;-)
Don't worry, I know how to calculate the output voltage of an LM1117-ADJ :) I would have calculated it first.
I assume you've used Vout = 1.25 (1+ R30/R28) or similar?
Bryce.
.
Quote from: Jeff_HxC2001 on 12:56, 29 March 11
Where ?
Ah darn I have just spent several minutes looking for it but can't find it... My imagination? Can anyone confirm whether there was a post about the demo's tracks?
Quote from: Jeff_HxC2001 on 12:56, 29 March 11
If you have no strange sdcard behaviors (sdcard not detected when the system is cold or warm...) no.
The issue is possible with Rev B boards when the power supply is over 5.3V and/or with some sdcard.
Ah I see. Every now and then I get the SD not found message when I first turn it on, I always took it out and reinserted it a couple of times and it got fixed. That's that, I guess... thanks.
Quote from: phi2x on 13:50, 29 March 11
I faced the same issue when parsing these dsk files on my emulator CPCBox.
But there is a twist in the end of the DSK format documentation: http://www.cpctech.org.uk/docs/dsk.html (http://www.cpctech.org.uk/docs/dsk.html)
As described there, tracks are stored in order, from 0 to (n-1). with n being the number of tracks of the dsk image.
So, the track numbering information inside Track Information Blocks are redundant and unnecessary, and can be safely discarded.
Thanks for these informations...
So this means that there are no possibility to have a dsk with some missing tracks ? Right ? I hope so ;-)
Quote from: Jeff_HxC2001 on 16:08, 29 March 11
Thanks for these informations...
So this means that there are no possibility to have a dsk with some missing tracks ? Right ? I hope so ;-)
With the standard dsk format, there will be data (at least the header exists) for all tracks. However, it may just be a track header, and number of sectors will be set to 0.
Each track header is a physical track on the disc. The actual number within the track doesn't necessarily have to be correct, and the same for the C value of the IDs.
In fact, I've found the only data to be reliable in the track header:
The ident (excluding \r\n)
number of sectors.
all others may not be accurate, including gap and filler byte.
It is also possible to have a dsk format, with less than 40 tracks, the rest should be treated as unformatted.
However, with the extended dsk format:
http://www.cpctech.org.uk/docs/extdsk.html (http://www.cpctech.org.uk/docs/extdsk.html)
It has information about the tracks in the header. The tracks are ordered as they would be on a physical disc.
A track size of 0, means unformatted and there may be no data for the track in the image.
But you can also have a track size of 1, which is just the header and no sectors, so also unformatted, or last, a header + sector data.
EDIT: With my emu I look at number of tracks and sides, then I treat them as if physically ordered:
track 0, track 1, track 2 etc
or
track 0 side 0, track 0 side 1, track 1 side 0, track 1 side 2 for 2 sided.
I ignore track number and side in the track header.
Quote from: phi2x on 13:50, 29 March 11
So, the track numbering information inside Track Information Blocks are redundant and unnecessary, and can be safely discarded.
No, because they can be different. Some copy protection systems (CPC) use this feature.
.
Quote from: TFM/FS on 21:04, 29 March 11
No, because they can be different. Some copy protection systems (CPC) use this feature.
mhhh i was afraid of that. That's why i actually use the track number present in the track header as the physical track number... So what is the truth? ;) Is the batman disk images broken or the DSK format itself is broken ?
With which tool the batman dsk file was created ?
Argh... this is getting more unstable than I'd like...
On the SD I was using, I copied a newly converted HFE. Then I started getting the [64] error... Removed that one file, fully formatted the card and copied everything back, now (with the original SD handler program) I'm getting the "could not load fat details (-2)!" error... What should I check?
Thanks again...
Quote from: Jeff_HxC2001 on 22:39, 29 March 11
mhhh i was afraid of that. That's why i actually use the track number present in the track header as the physical track number... So what is the truth? ;) Is the batman disk images broken or the DSK format itself is broken ?
With which tool the batman dsk file was created ?
well, there are lots of badly created dsk images out there.
the batman dsk was created with Arnold emulator.
EDIT: but you do have a point, I'll check Arnold's disk writing code ;)
EDIT: For single sided dsks, there was a bug in the writing code with the track numbers. Oops. So the batman disks are broken.
A few emus just ignore the track number in the header.
Quote from: arnoldemu on 11:51, 30 March 11
well, there are lots of badly created dsk images out there.
the batman dsk was created with Arnold emulator.
EDIT: but you do have a point, I'll check Arnold's disk writing code ;)
EDIT: For single sided dsks, there was a bug in the writing code with the track numbers. Oops. So the batman disks are broken.
A few emus just ignore the track number in the header.
Not mine ;-)
Quote from: Gryzor on 11:45, 30 March 11
Argh... this is getting more unstable than I'd like...
On the SD I was using, I copied a newly converted HFE. Then I started getting the [64] error... Removed that one file, fully formatted the card and copied everything back, now (with the original SD handler program) I'm getting the "could not load fat details (-2)!" error... What should I check?
Thanks again...
Check list:
-> Is the SDCard formatted in FAT32 ?
-> If rev B add the resistor...
-> Check the floppy cable
-> Is the jumper at the right position ?
Another point: try this beta version of the firmware:
http://hxc2001.free.fr/floppy_drive_emulator/SDHxCFirmware_beta.zip
Important : You need to use the beta version of the manager with this firmware !:
http://cpcwiki.eu/forum/index.php/topic,1750.msg21137.html#msg21137
-SD formatted as FAT32, yes.
-RevB indeed, but I never had a persistent problem before and I'm uncomfortable soldering anything on my previous emulator (especially since -second time I'm writing this today! - my last two attempts ended in a blown-up ZX and a non-working QL keyboard...)
-Floppy cable is fine - autoboot.hfe never fails to load anyhow, and it's almost brand new
-Jumper is as it always was :)
I'll try the beta, thanks! Will let you know...
Eh... I just booted it after several hours being away, before trying the new FW, and it worked first time... Seems totally random!
Will try the beta tho and will report in a few.
...
Ok, updated fine, SD card read fine, then copied the HFE that seemed to cause the problem, again SD is read fine. All is fine for now then... :)
Dodgy contact to the SD Card?
Bryce.
I've never seen one to tell you the truth, but in any case the first thing I always do when encountering removable media is, of course, remove and try again - this should solve it sooner or later I guess... whereas the problems I'm having are persistent for an amount of time - like, all morning it wouldn't work no matter what, now it works all the time :D
Quote from: Bryce on 18:11, 30 March 11
Dodgy contact to the SD Card?
Bryce.
Dodgy power supply... When it's cold -> doesn't work (>5.3V)
When getting warm -> <5.3V - Working again.
I recommend you to add the famous resistor and/or change/check your power supply...
Yes, I thought about that, that's why I said that it stopped working in the morning, when it was all warm and cozy, but worked this afternoon after being off for hours - and it worked first time! So it's not that either...
Quote from: Jeff_HxC2001 on 22:39, 29 March 11
mhhh i was afraid of that. That's why i actually use the track number present in the track header as the physical track number... So what is the truth? ;) Is the batman disk images broken or the DSK format itself is broken ?
With which tool the batman dsk file was created ?
I got no idea about the batman dsk image. But the sector ID of a sector must not contain valid data. When you write a sector, then you provide the sector ID data for the FDC, but you tell the FDC before which track and head you want to use. So the sector ID can contain everything, but this must not match the physical reality.
The good thing is... it looks like that nearly everything runs with the HxC. So it's fine.
Quote from: TFM/FS on 20:41, 30 March 11
I got no idea about the batman dsk image...
Now we know :) :
Quote from: arnoldemu on 11:51, 30 March 11
well, there are lots of badly created dsk images out there.
the batman dsk was created with Arnold emulator.
EDIT: but you do have a point, I'll check Arnold's disk writing code ;)
EDIT: For single sided dsks, there was a bug in the writing code with the track numbers. Oops. So the batman disks are broken.
A few emus just ignore the track number in the header.
Get the Update!
HxC2001 HeadQuarters : HxC Floppy Emulator (http://hxc2001.free.fr/floppy_drive_emulator/index.html#download)
Nah, if you're talking about the one posted a couple of days ago, it's just adding support for the Slim...
What is that Slim actually?
And no, there is another update from March.
Slim:
HXC Floppy Emulator SLIM (http://www.youtube.com/watch?v=bHx14xLwY78#)
My guess is the software update is to cover the Slim version, too.
Well, that sounds like a point. I'm glad with my blue version though :laugh:
New Update:
HxC2001 HeadQuarters : HxC Floppy Emulator (http://hxc2001.free.fr/floppy_drive_emulator/index.html#download)
Not much for us:
Quote
01 January 2016: HxCFloppyEmulator 2.1.4.0 (http://2.1.4.0)
New Loader : *.ANA AnaDisk file loader.
New Loader : VFDDAT file loader.
New Loader : Densei Sirius VFD DAT Loader.
New Writer : *.DIM writer.
New Writer : *.ADZ writer.
New Writer : *.TRD Writer.
New Loader : Atari ST *.STW Loader.
New Writer : Atari ST *.STW Writer.
New Writer : Atari ST *.ST Writer.
New Writer : Atari ST *.STX Writer.
STX Loader/Writer : Flakey bits mask support added, Loader/writer improved.
SCP Loader/Writer : Loader/writer improved.
D88 Loader : Gap3 setting corrected.
Dos disk browser : More disks layouts.
libhxcfe : New track support : AED6200P.
XML format definitions : Mictrotan 65 TANDOS.
Flux Stream Analyzer : Possible segmentation fault corrected.
Flux Stream Analyzer : Input filtering reduced.
Kryoflux Stream Loader (*XX.X.raw) / analyser : NFA over index support added.
Track editor : Add & Remove track functions added.
Track editor : RPM & Bitrate change functions added.
Track editor : Insertion function added.
Track editor : Negative offset support.
Disk viewer : Image CRC32, library version and file name displayed.
Disk viewer : Track(s) type displayed.
Disk viewer : Cells density displayed.
Progess bar added for the loaders/writers.
SD/USB Emulator setting window : Advanced pinout settings added.
Code sources fixes/changes for GCC, Clang and VS2015 x86 & x64 compilation support.