HP Forum Archive 16

[ Return to Index | Top of Index ]

Fragmenting in Hepax/NoVram? Message #1 Posted by Geir Isene on 7 Nov 2006, 4:32 p.m. Is a fragmented file system a possibility in Hepax ram in a NoVram/NoV-32? (I mean except for the possible left-over in each block)

Re: Fragmenting in Hepax/NoVram? Message #2 Posted by Diego Diaz on 8 Nov 2006, 3:25 a.m., in response to message #1 by Geir Isene Hi again, I assume "Fragmented" means for ex. pages #8, #9 and #B for the FILE SYSTEM while page #A is reserved for other purposes. If the above statement is correct, AFAIK and according to HEPAX documentation, FILE SYSTEM is organised in a chain-like fashion and must be kept "all-in-a-row" avoiding fragmentation. Further more, it is explicity recommended that pages taken off the FILESYS were always taken from the highest page number available. However, it should be interesting to configure a hand-made fragmented FILESYS by modifying the "Next block" pointers into one or more HEPAX RAM pages. Please let us know the results if you give it a go. Cheers. Diego.

Re: Fragmenting in Hepax/NoVram? Message #3 Posted by Miki Mihajlovic on 11 Nov 2006, 9:17 p.m., in response to message #2 by Diego Diaz I can happily report that the fragmented FS works just fine on MLDL2000 (what a wonderful toy is this turning out to be). I see no reason that wouldn't work on NOVRAM too. I have the following config: Page What ---- ----- 0x07 HEPAX 0x08 HEPRAM 0x09 HEPRAM 0x0A Sandbox Lower 0x0B Sandbox Upper 0x0C HEPRAM 0x0D HEPRAM 0x0E - 0x0F - with appropriate chain pointer changes at FE7 and FE8 offsets in pages 0x09 and 0x0C. HEPROOM gives 2610 empty registers, as you would expect for this 16k configuration, although I haven't tried to put any data into the FS. Best to all of you. Edited: 12 Nov 2006, 7:17 p.m.

[ Return to Index | Top of Index ]

Go back to the main exhibit hall