Update README with latest stats for the ROM version
diff --git a/README.md b/README.md
index 0100c57..773a956 100644
--- a/README.md
+++ b/README.md
@@ -39,6 +39,13 @@
 
 ![Screenshot of Contiki on CPC](/screenshot.png?raw=true "The Contiki Desktop.")
 
+This version was also converted to run as a ROM. With all the code being in ROM and overlaid with
+the framebuffer, this frees up 11K of extra space for loading and running apps when compared to
+the disk version. The 40K heap space is similar to what's available when BASIC is running.
+
+The ROM only has about 11K used, which means there is space for a bit more features to be added
+in there.
+
 Bitbox port
 -----------
 
@@ -103,6 +110,10 @@
 
 You will also need cpcfs from the cpctools project.
 
+To run Contiki, you will need a machine with a ROM disk as ROM 7 (AMSDOS was tested for now),
+and the Contiki ROM loaded as another ROM number. You need a keyboard as well, to type |CONTIKI
+when the machine is booted into BASIC.
+
 Steps
 -----
 
@@ -133,13 +144,13 @@
 for disc access. It runs entirely in the 64K base memory and doesn't use the
 banks or other expansion ROMs.
 
-Contiki uses the space usually reserved to BASIC, from &100 to &3700, for its
+Contiki uses some of the space usually reserved to BASIC, from &0100 to &0530, for its
 kernel. Since the Firmware and AMSDOS reserve all memory from &A700 up, this 
-leaves more than 30K of free RAM for applications. Not bad, but we can do better.
+leaves more than 41K of free RAM for applications.
 
 Current memory usage (with memstats.prg + desktop.prg running):
-* Heap size: 30681 bytes
-* Free memory: 26219 bytes
+* Heap size: 41424 bytes
+* Free memory: 36962 bytes
 
 Firmware-based CTK driver
 -------------------------
@@ -214,8 +225,7 @@
 to call Contiki methods from apps. Can SDCC handle this? We may need to generate
 syscall inlines or maybe we can do dirty tricks using the peephole to replace
 "CALL address" with "RST farcall ; dw address". This could leave 63+K of RAM
-for apps, and 32K of RAM for Contiki + screen drawing + FS. If space is scarce,
-it's probably time we try putting Contiki in one or two ROMs instead.
+for apps, and 32K of RAM for Contiki + screen drawing + FS.
 
 This is similar to the scheme used by CP/M+.