its the cf card. Half the ones i have dont work. here this one definitely works: https://www.amazon.com/dp/B07HM9849Z?psc=1&ref=ppx_pop_dt_b_product_detailsHi all, theres a lot to read through here, so Im just going to start over and ask my question straight up:
Im trying to get an XT-IDE rev 4 board working in an XT, but not having much luck.
It seems to be detecting the CF card, although it is showing some gibberish text. According to the problems page this can be caused by the wrong type of device being selected when the BIOS was configured. Ive tried a couple of different device types, but that doesnt seem to be helping. I either get "not found" or random characters. See the attached screenshot for my current settings.
When I am seeing random characters, I can fire up fdisk and try to create a partition. I can see the activity light on for about a second while this happens, but afterwards fdisk doesnt recognise any partitions, and I can go around in circles like this for as long as I want. So it seems like something is being written, but its not "sticking"?
Ive also tried a couple of different CF cards, one is a 32MB Cisco branded card, another is a 128MB somewhat generic "industrial" card. With the 128MB card, fdisk detected this as some 970 odd cylinders.
I tried creating a partition on the 32MB card on my Mac, and during boot XT-IDE will complain about the disk being not bootable, so I guess it sees the partition to some degree? fdisk does not, however.
Ive also been over the board with a magnifying glass to make sure all of my solder joints are looking good, none appear dry or particularly odd.
Edit: Ive also now just tried the R622 version of the BIOS (was previously using R624) along with the "XTCF PIO" mode, and in this case it seems that it was able to read back the model of CF card, although maybe only just. Sometimes It will just read back "UNIG" while other times it might read "UNIGEN FLASH".
Two things which I have done which are perhaps "non-standard", if they matter:
1. Im using my adapter at address 0x380/388 because I want to use the prototype board range (0x300-31F) for some upcoming projects (0x38X is for some SDLC/bisync adapter that I dont think I'll ever have). At this address things seem to be functional, but I have also tried it down at the default 0x30X just incase, but there was no change.
2. I have used mostly 74HCT parts because I just bought a bare board and dont hold any LS parts in stock. Some of these parts are AHCT which are a bit faster than HCT. Most specifically the AHCT parts are the two 04's, the 138, and the two 573's. Is anyone familiar enough with the circuitry to know whether these AHCT parts, maybe specifically the 04's since they are used to generate some delays, are just "too fast"? I havent tried it yet but I could solder in a small cap in one or both of the delay chains to try and slow them down a tad.
Any pointers appreciated.
Thanks!
See [here]. That displaying of the model information is not connected in any way with the contents of the CF card. You need to get the model information displaying consistently, then address possible issues with CF content.Edit: Ive also now just tried the R622 version of the BIOS (was previously using R624) along with the "XTCF PIO" mode, and in this case it seems that it was able to read back the model of CF card, although maybe only just. Sometimes It will just read back "UNIG" while other times it might read "UNIGEN FLASH".
I assume you have the Glitch Works R4 XT-IDE card https://www.minuszerodegrees.net/xtide/rev_4/XT-IDE Rev 4 - general.htmIm trying to get an XT-IDE rev 4 board working in an XT, but not having much luck.
Bad solder joints, Bad sockets, Bad IC/'s, Bad CF adapter, Bad CF card, Bad connection's, Take your pick.It seems to be detecting the CF card, although it is showing some gibberish text
So you can seemingly use FDISK to create a partition but upon reboot there is no partition created, That's not unusual if any of the above faults exist.When I am seeing random characters, I can fire up fdisk and try to create a partition. I can see the activity light on for about a second while this happens, but afterwards fdisk doesnt recognise any partitions, and I can go around in circles like this for as long as I want. So it seems like something is being written, but its not "sticking"?
What version of DOS are you using ?Ive also tried a couple of different CF cards, one is a 32MB Cisco branded card, another is a 128MB somewhat generic "industrial" card. With the 128MB card, fdisk detected this as some 970 odd cylinders.
XTCF PIO mode is used with the Lo-Tech XT-CF adapters not the GW R4Edit: Ive also now just tried the R622 version of the BIOS (was previously using R624) along with the "XTCF PIO" mode, and in this case it seems that it was able to read back the model of CF card, although maybe only just. Sometimes It will just read back "UNIG" while other times it might read "UNIGEN FLASH".
Where did you get the bare board from ?, I have used HCT / HC / LS series in my GW R4 boards with no problems though HCT are preferable.I have used mostly 74HCT parts because I just bought a bare board and dont hold any LS parts in stock
Welcome to these forums.Hello there - I believe this is my first post here!
That sounds a like the very first issue described at [here].A little update on my progress: a friend sent me his version of XTIDE, "XT" from 2013. That worked! I could see the drive, FDISK it, format it. I could install DOS 3.3 via SELECT. I can see the files and access the disk.
But I cannot boot from it. XT-IDE freezes on Booting C>>C and I have to power cycle.
It is highly probable that it, the XTIDE Universal BIOS (XUB), needs to be configured to suit the 'Glitch Works XT-IDE Rev 4'. See the {XTIDE Universal BIOS (XUB) - 'Device type' setting} section of [here]. Based on that, and assuming that your card is jumpered for hi-speed mode, the 'controller type' setting in the XUB would be configured for 'XTIDE rev2 or modded rev1'.I tried the current XT version available on the website but that does not recognise the drive at all.
But only if you need to. That hasn't been established yet. No one reading this has yet indicated that there is something special about the PS/2 model 30 8086 that requires a custom build of the XUB.I appreciate I should build my own version ...
Presumably, you are experimenting. It requires two actions:What parameter do I need to change to match the "compatibility" mode of the card?
So the subject card (plus IDE device) now fully works on the Pentium (booting 'and all'). But when you move the card (plus IDE device) to the PS/2 model 30 8086, the card does not work. Is my understanding correct?My R625 which works on my Pentium machine is set to "XTIDE Rev 2". That works on the Pentium but not on the PS/2. The card is jumpered for high-speed.
Ok. I kind of assumed that because there is a pre-built "PS2" ROM which does NOT support "XTIDE Rev1" or "Rev 2" so I thought one option was to build my own PS/2 version with that module included.But only if you need to. That hasn't been established yet. No one reading this has yet indicated that there is something special about the PS/2 model 30 8086 that requires a custom build of the XUB.
Fantastic, that is what I wanted to know, thanks.Presumably, you are experimenting. It requires two actions:
1. Change the jumpers on the Rev 4 card to the 'compatibility' setting (i.e. compatible with XTIDE Rev 1); and
2. Reconfigure the XUB: setting the device/controller type to 'XTIDE Rev 1'.
Let me find out exactly as things kind of changed after yesterday's tests. Thanks for pointing out that utility, I'll run it on my PS/2 and report back.So the subject card (plus IDE device) now fully works on the Pentium (booting 'and all'). But when you move the card (plus IDE device) to the PS/2 model 30 8086, the card does not work. Is my understanding correct?
What exactly is the symptom?
When the card is fitted in the PS/2 model 30 8086, does the RAYXTIDE tool at [here] report any problems with the XUB ?
I just realized that I made the USE_PS2 define with the assumption that PS/2 machines are a superset of the AT class machines. That's probably a mistake?Ok. I kind of assumed that because there is a pre-built "PS2" ROM which does NOT support "XTIDE Rev1" or "Rev 2" so I thought one option was to build my own PS/2 version with that module included.