ARLO FOR THE SERIES 5, SERIES 5MX and SERIES 7, Version 1.22 ============================================================ NOTE: Before you run any version of Arlo, you MUST do a cold reboot first because usually the device driver has been changed. Unfortunately, the device driver cannot be unloaded other then by rebooting. What's new in 1.22 ================== - Changed the heap size to be 512kb minimal and 16MB maximum. Arlo can now be loaded in low memory conditions. - Fixed problem in page table size. Arlo can now correctly load up to 16MB worth of kernel and initrd. - The driver has _not_ changed compared to 1.21. What's new in 1.21 ================== - Boot option in the .cfg file didn't work, it does now. - Fixed stupid bug in booting on the Series 5mx. - Reinstated "o" option in the expert menu to manually set the boot option What's new in 1.20 ================== - Arlo now works for the Series 5, 5mx and the Series 7 I've tested the Series 5 with a proper kernel and it boots ok. The series 5mx should still work, although I've not retested. The Series 7 does not fully work yet. The address translation works ok, but trying to boot some test kernel resutls in a crash. It's probably to do with the way the MMU gets disabled. Maybe I need to flush the cache first?! - For each of the three platforms we can use the exact same driver image. The only platform difference is that the EKern.exe UIDs seem to differ. Each time Arlo is started it will patch the driver file image with the UIDs of the local kernel (if needed). - To avoid copyright issues, I've removed the line editor code that was copied from the EPOC SDK and replaced it with a basic line editor I cooked up myself. - Some other bit and bobs: - Added the processor id in the information screen - Added the 'r' (for detect RAM) option in the expert menu. This reports the location of the RAM banks according to information in the EPOC kernel. - Hex numbers should entered as "0xabcd1234" and not abcd1234. Also made sure that we don't peek at address 0 (I make typos all the time and they get converted to 0) What's new in 1.10 ================== - Arlo now uses a config file for automatic booting. - This version of Arlo supports both the Series 5 and the Series 5MX. Said that, I don't own a Series 5 and could therefor only test it on a Series5mx. Feedback is appreciated on using it withe a Series5! - Note that the Series 5MX still has no kernel to boot, so it's pretty much for developers only. - Added a screen with some hardware info (select (a)advanced item and next (i)information). Installing ========== - Copy arlo.ldd to either c:\system\libs\ or d:\system\libs\ - Copy arlo.exe anywhere on c: or d: - arlo.exe will use config file c:\arlo.cfg or d:\arlo.cfg (searched for in that order). Copy the provided arlo.cfg and update as needed. Config file =========== See the supplied arlo.cfg for information on its format Running using the boot menu =========================== - Start arlo.exe - Arlo presents a boot menu with the info it has found from the config file. If no config file was present or could not be successfully interpreted the text will be displayed. - The default boot item has been marked by * - For the duration of the timeout you can select another boot or menu item. Advanced boot menu ================== - Presents more detailed info on how Arlo has interpreted the config file, including which file it has used. Experienced boot menu ===================== - This is basically the old Arlo. You can boot the "old" way by: - loading a kernel image and optionally an initrd image for example: l d:\vmlinuz l d:\initrd.gz b Building ======== - Unzip the source (with folder names) to the root of your epoc development drive. Building the driver ================== - change directory to \arlo\ldd - call "makmake arlo marm" - call "nmake -f arlo.marm" Building the console app ======================== - change directory to \arlo\app - call "makmake arlo marm" - call "nmake -f arlo.marm" Send suggestions or comments to: peter@yipton.demon.co.uk