RWAP Software

Thank you for your work... I'll have a look at it as soon as possible.

Using the RAM mode (like Residos) may (or may not) solve the problem. In RAM mode, a whole 16K RAM page is mapped (no ROM) and E7 should have no use. This could enable to work with the +D plugged in without changing anything into the interface. Fatware uses RAM pages 0 and 1, DemFir ram 2-3, +divIDE...

Out 23,72 or Out 23,104...
The first one sets the RAM in Read-Only mode, the second one sets it in Read/Write mode... So, if Residos needs to write in the ram paged at 0-16383, the second OUT should be better... at least if doc is correct.

The Manual has now been updated - the issue with the ResiDOS firmware was due to an error in the manual! According to Tygrys, the correct command to launch ResiDOS is: OUT 23,72: POKE 18455,237:POKE 18456,65:POKE 18457,199 PRINT USR 18455 Can someone please confirm? The updated version of the firmw...

Here is the programming algorithm from the datasheet (only extracts or summaries) File : 135891_DS.pdf Am29F040B 4 Megabit (512K x 8-bit) CMOS 5.0 Volt-only, Uniform Sector Flash Memory it explains that the memory is diided in 8 sectors of 64Kb Programming is done as a 4 bus-cycle operation : 2 unlo...

Implementation of greater ROM/RAM space on DiviDE Plus DivIDE Plus provides a total of 512K ROM and 512K RAM on the DivIDE Plus in order to enable much improved firmware to be written (this compares to the 8K ROM and 32K RAM available on the original DivIDE Hard Disk Interface). We decided on 512K ...

Well, I didn't try DemFir and I limited my +DivIDE tests to the strict minimum as I didn't make the proper partitionning on my CF card. I only did minimum tests on ResiDOS (I didn't find any need to use it as it's main point in for programming) Firmware selector can't do more than making the relevan...

+DivIDE more (G+Dos emulation) uses virtual floppies in the beginning of the CF card. It's said that sector 0 (Partition table) is safe. So, an idea would be to make two partitions on the CF card then delete the first one to leave room for the +DivIDE mode and use the second one as FAT. Windows don'...

In the documentation, it's said that a jumper allows to use the DivIDE+ to have ROM0/ROM1 replacement (with ROM0 in 0-15 and ROM1 in 16-31)... But I can only see 3 jumpers :
-CF master
-EEPROM protect
-+3 mode (ROMDIS1/ROMDIS2)

An issue with Fatware on a sinclair +2 (gray) : Under 48K mode, all is OK Under 128K mode (out 32765,0), the basic get screwed if you trigger an NMI to select an image. You may still enter commands but they don't get executed... If you use the OUT 23,32 to enable 128K mode, things go even worse... A...