QubATA v3.11.. - can't seem to re-partition my DOM drive...
Posted: Sat Jul 12, 2025 12:55 pm
Hi everyone (and esp. Alain Haoui - if you're here!)
I've finally gotten my Aurora+SGC system built and started to explore using the QubIDE (original board - but with the v2 GALs "1a/2a") expansion-card.
I had successfully attached and formatted a 128MB DOM (single partition) with the QubIDE v2.01 ROM/driver and was able to save and access files on it. At each reboot, a 'FAT problem' was reported, but no problems accessing the files.
I then re-programmed the ROM with Alain's v3.11 QubATA ROM image (driver_S_ROM). It successfully detected the existing DOM at boot-up (the boot-up diagnostics are very helpful!), but reported a problem with the FAT and couldn't mount the existing partition.
This wasn't a problem as I hadn't stored much there so proceeded to read Alain's excellent QubATA User Guide to understand how to re-initialise the DOM, following carefully the 'Typical sequence' steps listed on page 20 (Manual v3, from here: https://dilwyn.theqlforum.com/qlrom/QubATA311.zip)
However, at step #6 "WIN_DISK CREATE,<dev>,<part>,<size>", the command returns 'Disk full' - even though no partitions are listed by WIN_DISK "SUMMARY",<dev> (only the column headings are displayed.)
Any ideas?
One point to note - I had manually 'hacked' the ROM images (both the v2.01 and the v3.11) in a Hex editor to replace all occurrences of 'WIN' with 'QUB' - I also have a working SD-Card in this system that already uses the WIN device-name. Alain does explain that the RAM version can be CONFIGured to use the alternative device-name, but I wasn't sure how relevant that was for the ROM image, so did it by hand - which seemed to work under v2.01...
Thanks in advance for your thoughts...
I've finally gotten my Aurora+SGC system built and started to explore using the QubIDE (original board - but with the v2 GALs "1a/2a") expansion-card.
I had successfully attached and formatted a 128MB DOM (single partition) with the QubIDE v2.01 ROM/driver and was able to save and access files on it. At each reboot, a 'FAT problem' was reported, but no problems accessing the files.
I then re-programmed the ROM with Alain's v3.11 QubATA ROM image (driver_S_ROM). It successfully detected the existing DOM at boot-up (the boot-up diagnostics are very helpful!), but reported a problem with the FAT and couldn't mount the existing partition.
This wasn't a problem as I hadn't stored much there so proceeded to read Alain's excellent QubATA User Guide to understand how to re-initialise the DOM, following carefully the 'Typical sequence' steps listed on page 20 (Manual v3, from here: https://dilwyn.theqlforum.com/qlrom/QubATA311.zip)
However, at step #6 "WIN_DISK CREATE,<dev>,<part>,<size>", the command returns 'Disk full' - even though no partitions are listed by WIN_DISK "SUMMARY",<dev> (only the column headings are displayed.)
Any ideas?
One point to note - I had manually 'hacked' the ROM images (both the v2.01 and the v3.11) in a Hex editor to replace all occurrences of 'WIN' with 'QUB' - I also have a working SD-Card in this system that already uses the WIN device-name. Alain does explain that the RAM version can be CONFIGured to use the alternative device-name, but I wasn't sure how relevant that was for the ROM image, so did it by hand - which seemed to work under v2.01...
Thanks in advance for your thoughts...