I've been anxiously awaiting the extended memory feature for the ram drive but even though the option is listed in the OS4.1FEupdate1 documentation, it doesn't work. Is there a reason why users didn't get the extended memory feature in the update1??

iirc (and i'm sure i'm not) i was told that it won't be part of this bugfix package as the extmem feature relies on updated system components which relies on other updated system components which are either not ready for release, still in alpha/beta test and/or not fit for release yet.

I'm as anxious as you for this new feature as i'd like to plant it into some of my ports (which i'm probably not even able to do anyway)

otoh i'm also anxiously waiting for multicore...so...

I'll watch this space

If slaughterhouses had glass walls, everyone would be a vegetarian. ~ Sir Paul McCartney-Did everything just taste purple for a second? ~ Philip J. Fry-Ain't got no cash, ain't got no style, ladies vomit when I smile. ~ Dr. John Zoidberg

Me too. I did notice one strange thing about setting prefs for the new ram-handler. If there several lines of text in the shell window, entering the command to show or change the ram-handler prefs causes the console to scroll up when the results are printed; even when the output isn't at the bottom of the shell window. Try this:

1. Open a new shell window to full screen height and enter the 'avail' command twice.2. Enter "SYS:Kickstart/ram-handler.kmod show".3. The output of the 'avail' command will be scrolled off the top of the shell window when the ram-handler command is executed (even though the text hasn't reached the bottom of the shell window).

Me too. I did notice one strange thing about setting prefs for the new ram-handler. If there several lines of text in the shell window, entering the command to show or change the ram-handler prefs causes the console to scroll up when the results are printed; even when the output isn't at the bottom of the shell window. Try this:

1. Open a new shell window to full screen height and enter the 'avail' command twice.2. Enter "SYS:Kickstart/ram-handler.kmod show".3. The output of the 'avail' command will be scrolled off the top of the shell window when the ram-handler command is executed (even though the text hasn't reached the bottom of the shell window).

I get the same effect here, but it seems to be intended to do that.It looks like as if the command is doing the "scroll everything out and place my output to the top of the window/shell/CON" on purpose

oh and btw, seems like the extmem feature didn't make it into this update et al

Me too. I did notice one strange thing about setting prefs for the new ram-handler. If there several lines of text in the shell window, entering the command to show or change the ram-handler prefs causes the console to scroll up when the results are printed; even when the output isn't at the bottom of the shell window. Try this:

1. Open a new shell window to full screen height and enter the 'avail' command twice.2. Enter "SYS:Kickstart/ram-handler.kmod show".3. The output of the 'avail' command will be scrolled off the top of the shell window when the ram-handler command is executed (even though the text hasn't reached the bottom of the shell window).

That's just the command issue console intructions to align the output with the top of the screen, nothing to see there (bug wise) move along...