On 2024-01-21 15:45:09, Michael Drake wrote:
> Hi Michael,
>
> I'm sorry it's taken so long to get back to you.
No problem, I wasn't expecting it to be a quick review. I've pushed a
few more commits to my branch that fix all of these issues (except
-pedantic, see below).
> When I tried building I got a lot of `-Werror=pedantic` warnings due to the use
> of a libwapcaplet macro....
>
> So we'd need to drop the -pedantic in the Makefile.
I actually don't see these with gcc-13.2.1? Thankfully this is the
easiest / least-important of the issues. I can still drop the flag if
you want me to do it -- I'd just feel better if I could see the errors
disappear as a result of my change.
> I also had warnings about `fill_opacity_type` and `stroke_opacity_type` being
> set but unused in `svgtiny_parse_styles`. I simply called those computed style
> getters without assigning their return value.
Fixed, thanks. These slipped through because I was accidentally
clobbering my WARNFLAGS.
> In the function `node_has_name`
>
> https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l643
>
> It's doing a `lwc_string_isequal` between `qname->name` (Wapcapplet string) and
> `state->interned_universal` (DOM string), which won't work. I changed
> it to a call to
> `dom_string_lwc_isequal` locally.
Fixed.
> Also I added a `break` before the `default` case in this `switch`, to
> stop it asserting when built with `make VARIANT=debug`:
>
> https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l1941
Fixed.
> With those changes I tried running it but found it was unstable in NetSurf.
>
> I haven't done very much testing but I could see issues running the libsvgtiny
> test runner binary under valgrind:
I was using lwc_string_destroy() where I should have been using
lwc_string_unref(). I fixed that one, and re-ran the other tests under
valgrind. They all come up clean now. Hopefully that was the cause of
the NetSurf instability.
Friday, 26 January 2024
Sunday, 21 January 2024
[netsurf-dev] Re: Pull request: CSS support for libsvgtiny
Hi Michael,
I'm sorry it's taken so long to get back to you.
I've had a look now.
When I tried building I got a lot of `-Werror=pedantic` warnings due to the use
of a libwapcaplet macro. For example:
src/svgtiny_css.c: In function 'node_name':
include/libwapcaplet/libwapcaplet.h:137:29: error:
ISO C forbids braced-groups within expressions [-Werror=pedantic]
So we'd need to drop the -pedantic in the Makefile.
I also had warnings about `fill_opacity_type` and `stroke_opacity_type` being
set but unused in `svgtiny_parse_styles`. I simply called those computed style
getters without assigning their return value.
In the function `node_has_name`
https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l643
It's doing a `lwc_string_isequal` between `qname->name` (Wapcapplet string) and
`state->interned_universal` (DOM string), which won't work. I changed
it to a call to
`dom_string_lwc_isequal` locally.
Also I added a `break` before the `default` case in this `switch`, to
stop it asserting when built with `make VARIANT=debug`:
https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l1941
With those changes I tried running it but found it was unstable in NetSurf.
I haven't done very much testing but I could see issues running the libsvgtiny
test runner binary under valgrind:
make test
valgrind --track-origins=yes \
build-x86_64-linux-gnu-x86_64-linux-gnu-release-lib-static/test_decode_svg
\
test/css/lang.svg
Sorry again for taking so long to respond!
Best regards,
Michael
On Mon, 20 Nov 2023 at 17:27, Michael Orlitzky <michael@orlitzky.com> wrote:
>
> As promised, and only a month late. My branch is available at,
>
> https://gitweb.michael.orlitzky.com/libsvgtiny.git libcss
>
> For best results, you should also apply the libcss patch I recently
> posted that makes fill- and stroke-opacity inherited properties.
>
> No major issues remain. There's a test suite in test/css consisting
> of a bunch of SVG files that you can open side-by-side in the
> libsvgtiny example program and your favorite image viewer. With the
> libcss patch, they all pass (compared to firefox). Without it, two
> fail.
>
> If you recall, there was some concern about the licensing of the
> select handlers. I think I spent enough time learning and rewriting
> the handlers to alleviate those concerns; I ultimately did not copy
> anything from NetSurf, although naturally many of the handlers look
> similar (and of course I reimplemented them *after* looking at the
> NetSurf handlers, so you be the judge).
>
> A summary of the changes follows.
>
> ----------------------------------------------------------------
> Michael Orlitzky (88):
> src/svgtiny_internal.h: removed commented libcss stub
> src/svgtiny.c: remove old misleading libcss comments
> Makefile: build against libcss
> README: mention that libcss is required
> src/svgtiny_internal.h: add CSS context to parser state
> src/svgtiny_strings.h: add "media" to the list of strings
> include/svgtiny.h: add new error constant svgtiny_LIBCSS_ERROR
> README: document the new svgtiny_LIBCSS_ERROR code
> src/svgtiny.c: initialize the libcss context in svgtiny_parse()
> src/svgtiny.c: add impotent svgtiny_preparse_styles() function
> src/svgtiny_css.c: new file with new svgtiny_resolve_url() function
> src/svgtiny_internal.h: add svgtiny_resolve_url() prototype
> src/Makefile: add the new svgtiny_css.c to the list of sources
> src/svgtiny.c: add svgtiny_parse_style_element() function and use it
> src/svgtiny_css.c: new function svgtiny_create_stylesheet()
> src/svgtiny_internal.h: add svgtiny_create_stylesheet() prototype
> src/svgtiny.c: use svgtiny_create_stylesheet() to parse <style>
> src/svgtiny_internal.h: drop svgtiny_resolve_url() prototype
> src/svgtiny.c: add svgtiny_parse_style_inline() function
> src/svgtiny.c: parse inline stylesheet in svgtiny_parse_paint_attributes()
> src/svgtiny{.c,_internal.h}: intern SVG's XML namespace URI
> src/svgtiny_css.c: implement node_name() select handler
> src/svgtiny_css.c: implement node_classes() select handler
> src/svgtiny_strings.h: intern "id" for libcss
> src/svgtiny_css.c: implement node_id() select handler
> src/svgtiny_css.c: implement named_parent_node() select handler
> src/svgtiny_css.c: implement named_sibling_node() select handler
> src/svgtiny_css.c: implement named_generic_sibling_node() select handler
> src/svgtiny_css.c: implement parent_node() select handler
> src/svgtiny_css.c: implement sibling_node() select handler
> src/svgtiny_strings.h: intern the universal selector string "*"
> src/svgtiny_css.c: implement node_has_name() select handler
> src/svgtiny_css.c: implement node_has_class() select handler
> src/svgtiny_css.c: implement node_has_id() select handler
> src/svgtiny_css.c: implement node_has_attribute() select handler
> src/svgtiny_css.c: implement node_has_attribute_equal() select handler
> src/svgtiny_css.c: implement node_has_attribute_dashmatch() select handler
> src/svgtiny_css.c: implement node_has_attribute_includes() select handler
> src/svgtiny_css.c: implement node_has_attribute_prefix() select handler
> src/svgtiny_css.c: implement node_has_attribute_suffix() select handler
> src/svgtiny_css.c: implement node_has_attribute_substring() select handler
> src/svgtiny_css.c: implement node_is_root() select handler
> src/svgtiny_css.c: implement node_count_siblings() select handler
> src/svgtiny_css.c: implement node_is_empty() select handler
> src/svgtiny_css.c: implement node_is_link() select handler
> src/svgtiny_css.c: implement node_is_hover() select handler
> src/svgtiny_css.c: implement node_is_active() select handler
> src/svgtiny_css.c: implement node_is_focus() select handler
> src/svgtiny_css.c: implement node_is_enabled() select handler
> src/svgtiny_css.c: implement node_is_disabled() select handler
> src/svgtiny_css.c: implement node_is_checked() select handler
> src/svgtiny_css.c: implement node_is_target() select handler
> src/svgtiny_css.c: case-insensitivity for node_has_attribute_substring()
> src/svgtiny_css.c: implement node_is_lang() select handler
> src/svgtiny_css.c: implement ua_default_for_property() select handler
> src/svgtiny_css.c: implement node_is_visited() select handler
> src/svgtiny_strings.h: intern a "userdata" key string
> src/svgtiny_css.c: implement set_libcss_node_data() select handler
> src/svgtiny_css.c: implement get_libcss_node_data() select handler
> src/svgtiny_css.c: implement node_presentational_hint() select handler
> src/svgtiny_css.c: implement named_ancestor_node() select handler
> src/svgtiny_css.c: define a css_select_handler
> src/svgtiny_css.c: add user handler function
> src/svgtiny_css.c: use our userdata handler in set_libcss_node_data()
> src/svgtiny_css.c: add svgtiny_select_style() wrapper
> src/svgtiny_internal.h: add svgtiny_select_style() to the header
> src/svgtiny_internal.h: add fill/stroke_opacity to the parse state struct
> src/svgtiny.c: eliminate pointless NULL check
> examples/svgtiny_display_x11.c: handle svgtiny_LIBCSS_ERROR
> test/decode_svg.c: handle svgtiny_LIBCSS_ERROR
> src/svgtiny.c: parse styles in svgtiny_parse_paint_attributes()
> include/svgtiny.h: add fill_opacity and stroke_opacity to svgtiny_shape
> src/svgtiny.c: set shape opacities from the parser state
> examples/svgtiny_display_x11.c: use opacity information
> src/svgtiny.c: update the docstring for svgtiny_parse_svg()
> src/svgtiny.c: use separate function for style application
> src/svgtiny_internal.h: add parent style to the parser state
> src/svgtiny*.{c,h}: move the libcss unit context into the parser state
> src/svgtiny.c: implement composition of parent styles
> src/svgtiny_css.c: add some default user-agent properties after all
> src/svgtiny.c: remove parent == NULL hack
> examples/GNUmakefile: add a GNUmakefile for the example program
> examples/svgtiny_display_x11.c: update build instructions
> examples/.gitignore: ignore the compiled example program
> src/svgtiny.c: use case-sensitive comparisons for SVG element names
> test/css: add some visually-verified test cases for our new features
> src/svgtiny_css.c: clean trailing newlines
> src/svgtiny.c: whitespace cleanup (spaces to tabs)
>
> Makefile | 8 +-
> README | 13 +-
> examples/.gitignore | 2 +
> examples/GNUmakefile | 20 +
> examples/svgtiny_display_x11.c | 55 +-
> include/svgtiny.h | 5 +-
> src/Makefile | 2 +-
> src/svgtiny.c | 494 ++++++++++--
> src/svgtiny_css.c | 2069 ++++++++++++++++++++++++++++++++++++++++++++++++++
> src/svgtiny_internal.h | 37 +-
> src/svgtiny_strings.h | 4 +
> test/css/README | 11 +
> test/css/attributes.svg | 94 +++
> test/css/case-sensitive-elements.svg | 19 +
> test/css/empty-pseudo-class.svg | 33 +
> test/css/id-and-class.svg | 49 ++
> test/css/inherit.svg | 43 ++
> test/css/inline.svg | 31 +
> test/css/lang.svg | 32 +
> test/css/link-pseudo-class.svg | 36 +
> test/css/node-name.svg | 40 +
> test/css/nth-child.svg | 52 ++
> test/css/root.svg | 25 +
> test/css/siblings-and-descendants.svg | 64 ++
> test/css/styles-at-end.svg | 29 +
> test/decode_svg.c | 3 +
> 26 files changed, 3169 insertions(+), 101 deletions(-)
> create mode 100644 examples/.gitignore
> create mode 100644 examples/GNUmakefile
> create mode 100644 src/svgtiny_css.c
> create mode 100644 test/css/README
> create mode 100644 test/css/attributes.svg
> create mode 100644 test/css/case-sensitive-elements.svg
> create mode 100644 test/css/empty-pseudo-class.svg
> create mode 100644 test/css/id-and-class.svg
> create mode 100644 test/css/inherit.svg
> create mode 100644 test/css/inline.svg
> create mode 100644 test/css/lang.svg
> create mode 100644 test/css/link-pseudo-class.svg
> create mode 100644 test/css/node-name.svg
> create mode 100644 test/css/nth-child.svg
> create mode 100644 test/css/root.svg
> create mode 100644 test/css/siblings-and-descendants.svg
> create mode 100644 test/css/styles-at-end.svg
> _______________________________________________
> netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
> To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
I'm sorry it's taken so long to get back to you.
I've had a look now.
When I tried building I got a lot of `-Werror=pedantic` warnings due to the use
of a libwapcaplet macro. For example:
src/svgtiny_css.c: In function 'node_name':
include/libwapcaplet/libwapcaplet.h:137:29: error:
ISO C forbids braced-groups within expressions [-Werror=pedantic]
So we'd need to drop the -pedantic in the Makefile.
I also had warnings about `fill_opacity_type` and `stroke_opacity_type` being
set but unused in `svgtiny_parse_styles`. I simply called those computed style
getters without assigning their return value.
In the function `node_has_name`
https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l643
It's doing a `lwc_string_isequal` between `qname->name` (Wapcapplet string) and
`state->interned_universal` (DOM string), which won't work. I changed
it to a call to
`dom_string_lwc_isequal` locally.
Also I added a `break` before the `default` case in this `switch`, to
stop it asserting when built with `make VARIANT=debug`:
https://gitweb.michael.orlitzky.com/?p=libsvgtiny.git;a=blob;f=src/svgtiny_css.c;h=7e203a2b70f09b3127108aca03f18e6269a9d582;hb=refs/heads/libcss#l1941
With those changes I tried running it but found it was unstable in NetSurf.
I haven't done very much testing but I could see issues running the libsvgtiny
test runner binary under valgrind:
make test
valgrind --track-origins=yes \
build-x86_64-linux-gnu-x86_64-linux-gnu-release-lib-static/test_decode_svg
\
test/css/lang.svg
Sorry again for taking so long to respond!
Best regards,
Michael
On Mon, 20 Nov 2023 at 17:27, Michael Orlitzky <michael@orlitzky.com> wrote:
>
> As promised, and only a month late. My branch is available at,
>
> https://gitweb.michael.orlitzky.com/libsvgtiny.git libcss
>
> For best results, you should also apply the libcss patch I recently
> posted that makes fill- and stroke-opacity inherited properties.
>
> No major issues remain. There's a test suite in test/css consisting
> of a bunch of SVG files that you can open side-by-side in the
> libsvgtiny example program and your favorite image viewer. With the
> libcss patch, they all pass (compared to firefox). Without it, two
> fail.
>
> If you recall, there was some concern about the licensing of the
> select handlers. I think I spent enough time learning and rewriting
> the handlers to alleviate those concerns; I ultimately did not copy
> anything from NetSurf, although naturally many of the handlers look
> similar (and of course I reimplemented them *after* looking at the
> NetSurf handlers, so you be the judge).
>
> A summary of the changes follows.
>
> ----------------------------------------------------------------
> Michael Orlitzky (88):
> src/svgtiny_internal.h: removed commented libcss stub
> src/svgtiny.c: remove old misleading libcss comments
> Makefile: build against libcss
> README: mention that libcss is required
> src/svgtiny_internal.h: add CSS context to parser state
> src/svgtiny_strings.h: add "media" to the list of strings
> include/svgtiny.h: add new error constant svgtiny_LIBCSS_ERROR
> README: document the new svgtiny_LIBCSS_ERROR code
> src/svgtiny.c: initialize the libcss context in svgtiny_parse()
> src/svgtiny.c: add impotent svgtiny_preparse_styles() function
> src/svgtiny_css.c: new file with new svgtiny_resolve_url() function
> src/svgtiny_internal.h: add svgtiny_resolve_url() prototype
> src/Makefile: add the new svgtiny_css.c to the list of sources
> src/svgtiny.c: add svgtiny_parse_style_element() function and use it
> src/svgtiny_css.c: new function svgtiny_create_stylesheet()
> src/svgtiny_internal.h: add svgtiny_create_stylesheet() prototype
> src/svgtiny.c: use svgtiny_create_stylesheet() to parse <style>
> src/svgtiny_internal.h: drop svgtiny_resolve_url() prototype
> src/svgtiny.c: add svgtiny_parse_style_inline() function
> src/svgtiny.c: parse inline stylesheet in svgtiny_parse_paint_attributes()
> src/svgtiny{.c,_internal.h}: intern SVG's XML namespace URI
> src/svgtiny_css.c: implement node_name() select handler
> src/svgtiny_css.c: implement node_classes() select handler
> src/svgtiny_strings.h: intern "id" for libcss
> src/svgtiny_css.c: implement node_id() select handler
> src/svgtiny_css.c: implement named_parent_node() select handler
> src/svgtiny_css.c: implement named_sibling_node() select handler
> src/svgtiny_css.c: implement named_generic_sibling_node() select handler
> src/svgtiny_css.c: implement parent_node() select handler
> src/svgtiny_css.c: implement sibling_node() select handler
> src/svgtiny_strings.h: intern the universal selector string "*"
> src/svgtiny_css.c: implement node_has_name() select handler
> src/svgtiny_css.c: implement node_has_class() select handler
> src/svgtiny_css.c: implement node_has_id() select handler
> src/svgtiny_css.c: implement node_has_attribute() select handler
> src/svgtiny_css.c: implement node_has_attribute_equal() select handler
> src/svgtiny_css.c: implement node_has_attribute_dashmatch() select handler
> src/svgtiny_css.c: implement node_has_attribute_includes() select handler
> src/svgtiny_css.c: implement node_has_attribute_prefix() select handler
> src/svgtiny_css.c: implement node_has_attribute_suffix() select handler
> src/svgtiny_css.c: implement node_has_attribute_substring() select handler
> src/svgtiny_css.c: implement node_is_root() select handler
> src/svgtiny_css.c: implement node_count_siblings() select handler
> src/svgtiny_css.c: implement node_is_empty() select handler
> src/svgtiny_css.c: implement node_is_link() select handler
> src/svgtiny_css.c: implement node_is_hover() select handler
> src/svgtiny_css.c: implement node_is_active() select handler
> src/svgtiny_css.c: implement node_is_focus() select handler
> src/svgtiny_css.c: implement node_is_enabled() select handler
> src/svgtiny_css.c: implement node_is_disabled() select handler
> src/svgtiny_css.c: implement node_is_checked() select handler
> src/svgtiny_css.c: implement node_is_target() select handler
> src/svgtiny_css.c: case-insensitivity for node_has_attribute_substring()
> src/svgtiny_css.c: implement node_is_lang() select handler
> src/svgtiny_css.c: implement ua_default_for_property() select handler
> src/svgtiny_css.c: implement node_is_visited() select handler
> src/svgtiny_strings.h: intern a "userdata" key string
> src/svgtiny_css.c: implement set_libcss_node_data() select handler
> src/svgtiny_css.c: implement get_libcss_node_data() select handler
> src/svgtiny_css.c: implement node_presentational_hint() select handler
> src/svgtiny_css.c: implement named_ancestor_node() select handler
> src/svgtiny_css.c: define a css_select_handler
> src/svgtiny_css.c: add user handler function
> src/svgtiny_css.c: use our userdata handler in set_libcss_node_data()
> src/svgtiny_css.c: add svgtiny_select_style() wrapper
> src/svgtiny_internal.h: add svgtiny_select_style() to the header
> src/svgtiny_internal.h: add fill/stroke_opacity to the parse state struct
> src/svgtiny.c: eliminate pointless NULL check
> examples/svgtiny_display_x11.c: handle svgtiny_LIBCSS_ERROR
> test/decode_svg.c: handle svgtiny_LIBCSS_ERROR
> src/svgtiny.c: parse styles in svgtiny_parse_paint_attributes()
> include/svgtiny.h: add fill_opacity and stroke_opacity to svgtiny_shape
> src/svgtiny.c: set shape opacities from the parser state
> examples/svgtiny_display_x11.c: use opacity information
> src/svgtiny.c: update the docstring for svgtiny_parse_svg()
> src/svgtiny.c: use separate function for style application
> src/svgtiny_internal.h: add parent style to the parser state
> src/svgtiny*.{c,h}: move the libcss unit context into the parser state
> src/svgtiny.c: implement composition of parent styles
> src/svgtiny_css.c: add some default user-agent properties after all
> src/svgtiny.c: remove parent == NULL hack
> examples/GNUmakefile: add a GNUmakefile for the example program
> examples/svgtiny_display_x11.c: update build instructions
> examples/.gitignore: ignore the compiled example program
> src/svgtiny.c: use case-sensitive comparisons for SVG element names
> test/css: add some visually-verified test cases for our new features
> src/svgtiny_css.c: clean trailing newlines
> src/svgtiny.c: whitespace cleanup (spaces to tabs)
>
> Makefile | 8 +-
> README | 13 +-
> examples/.gitignore | 2 +
> examples/GNUmakefile | 20 +
> examples/svgtiny_display_x11.c | 55 +-
> include/svgtiny.h | 5 +-
> src/Makefile | 2 +-
> src/svgtiny.c | 494 ++++++++++--
> src/svgtiny_css.c | 2069 ++++++++++++++++++++++++++++++++++++++++++++++++++
> src/svgtiny_internal.h | 37 +-
> src/svgtiny_strings.h | 4 +
> test/css/README | 11 +
> test/css/attributes.svg | 94 +++
> test/css/case-sensitive-elements.svg | 19 +
> test/css/empty-pseudo-class.svg | 33 +
> test/css/id-and-class.svg | 49 ++
> test/css/inherit.svg | 43 ++
> test/css/inline.svg | 31 +
> test/css/lang.svg | 32 +
> test/css/link-pseudo-class.svg | 36 +
> test/css/node-name.svg | 40 +
> test/css/nth-child.svg | 52 ++
> test/css/root.svg | 25 +
> test/css/siblings-and-descendants.svg | 64 ++
> test/css/styles-at-end.svg | 29 +
> test/decode_svg.c | 3 +
> 26 files changed, 3169 insertions(+), 101 deletions(-)
> create mode 100644 examples/.gitignore
> create mode 100644 examples/GNUmakefile
> create mode 100644 src/svgtiny_css.c
> create mode 100644 test/css/README
> create mode 100644 test/css/attributes.svg
> create mode 100644 test/css/case-sensitive-elements.svg
> create mode 100644 test/css/empty-pseudo-class.svg
> create mode 100644 test/css/id-and-class.svg
> create mode 100644 test/css/inherit.svg
> create mode 100644 test/css/inline.svg
> create mode 100644 test/css/lang.svg
> create mode 100644 test/css/link-pseudo-class.svg
> create mode 100644 test/css/node-name.svg
> create mode 100644 test/css/nth-child.svg
> create mode 100644 test/css/root.svg
> create mode 100644 test/css/siblings-and-descendants.svg
> create mode 100644 test/css/styles-at-end.svg
> _______________________________________________
> netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
> To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Re: [Rpcemu] Message meaning
In article <f35427265b.MSPro@Marker.Dommel.be>,
Steve Royd-Marker <riscos@markerdesign.be> wrote:
> Hi Dave.
> I suppose these mails I have been getting, about RPCEmu are not really
> intended for me but I have been getting them because I have been put
> in CC?
> Regards, Steve Royd marker
Hi Steve,
No CC was involved, and as Frank has noted, "You're on the rpcemu mailing
list..." :-)
As I'd been having a problem with RPCEmu and LanMan98, I thought it
courteous to let the folks here who'd been attempting to help me with the
problem know what the actual answer was...
The answer/reminder was presented to me in a Newsgroup elsewhere... :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Steve Royd-Marker <riscos@markerdesign.be> wrote:
> Hi Dave.
> I suppose these mails I have been getting, about RPCEmu are not really
> intended for me but I have been getting them because I have been put
> in CC?
> Regards, Steve Royd marker
Hi Steve,
No CC was involved, and as Frank has noted, "You're on the rpcemu mailing
list..." :-)
As I'd been having a problem with RPCEmu and LanMan98, I thought it
courteous to let the folks here who'd been attempting to help me with the
problem know what the actual answer was...
The answer/reminder was presented to me in a Newsgroup elsewhere... :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Message meaning
In article <f35427265b.MSPro@Marker.Dommel.be>,
Steve Royd-Marker <riscos@markerdesign.be> wrote:
> Hi Dave.
> I suppose these mails I have been getting, about RPCEmu are not really
> intended for me but I have been getting them because I have been put
> in CC?
> Regards, Steve Royd marker
You're on the rpcemu mailing list, Steve.
Regards,
--
Frank
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Steve Royd-Marker <riscos@markerdesign.be> wrote:
> Hi Dave.
> I suppose these mails I have been getting, about RPCEmu are not really
> intended for me but I have been getting them because I have been put
> in CC?
> Regards, Steve Royd marker
You're on the rpcemu mailing list, Steve.
Regards,
--
Frank
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Message meaning
Hi Dave.
I suppose these mails I have been getting, about RPCEmu are not really
intended for me but I have been getting them because I have been put
in CC?
Regards, Steve Royd marker
In message <5b25278318dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:
> In article <5b23446ec7dave@triffid.co.uk>,
> Dave <dave@triffid.co.uk> wrote:
> [Snip]
>> Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
>> the PC side.
>> Something I've had to do in the past on other Win/RISC OS machines, but
>> totally forgot...
>> Dave
>> Age, pudding brain and medication... :-(
> So RPCEmu and LM98 are now working okay.
> Dave
--
Vriendelijke groeten, Steve
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
I suppose these mails I have been getting, about RPCEmu are not really
intended for me but I have been getting them because I have been put
in CC?
Regards, Steve Royd marker
In message <5b25278318dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:
> In article <5b23446ec7dave@triffid.co.uk>,
> Dave <dave@triffid.co.uk> wrote:
> [Snip]
>> Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
>> the PC side.
>> Something I've had to do in the past on other Win/RISC OS machines, but
>> totally forgot...
>> Dave
>> Age, pudding brain and medication... :-(
> So RPCEmu and LM98 are now working okay.
> Dave
--
Vriendelijke groeten, Steve
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Friday, 19 January 2024
Re: [Rpcemu] Message meaning
In article <5b23446ec7dave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
[Snip]
> Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
> the PC side.
> Something I've had to do in the past on other Win/RISC OS machines, but
> totally forgot...
> Dave
> Age, pudding brain and medication... :-(
So RPCEmu and LM98 are now working okay.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Dave <dave@triffid.co.uk> wrote:
[Snip]
> Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
> the PC side.
> Something I've had to do in the past on other Win/RISC OS machines, but
> totally forgot...
> Dave
> Age, pudding brain and medication... :-(
So RPCEmu and LM98 are now working okay.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Monday, 15 January 2024
Re: [Rpcemu] Message meaning
In article <5b22a78efcdave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
> Right, now that's setup, back to my original question which I'm taking
> to comp.sys.acorn.networking as it's also causing problem on other VRPC
> installs as well as RPCEmu. :-(
> Dave
Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
the PC side.
Something I've had to do in the past on other Win/RISC OS machines, but
totally forgot...
Dave
Age, pudding brain and medication... :-(
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Dave <dave@triffid.co.uk> wrote:
> Right, now that's setup, back to my original question which I'm taking
> to comp.sys.acorn.networking as it's also causing problem on other VRPC
> installs as well as RPCEmu. :-(
> Dave
Bob Latham has reminded me about adjusting the IRPStacksize in RegEdit on
the PC side.
Something I've had to do in the past on other Win/RISC OS machines, but
totally forgot...
Dave
Age, pudding brain and medication... :-(
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Sunday, 14 January 2024
[Rpcemu] Message meaning
In article <5b223e4b8cdave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:
[Snip]
> Aha! that's much clearer, and I now have the sym links in place and
> working, including one for memory sticks.
> Thanks Michael, much appreciated. :-)
> Dave
Right, now that's setup, back to my original question which I'm taking to
comp.sys.acorn.networking as it's also causing problem on other VRPC
installs as well as RPCEmu. :-(
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Dave <dave@triffid.co.uk> wrote:
[Snip]
> Aha! that's much clearer, and I now have the sym links in place and
> working, including one for memory sticks.
> Thanks Michael, much appreciated. :-)
> Dave
Right, now that's setup, back to my original question which I'm taking to
comp.sys.acorn.networking as it's also causing problem on other VRPC
installs as well as RPCEmu. :-(
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Saturday, 13 January 2024
Re: [Rpcemu] Message meaning
In article <acd5bd50-2173-a446-b884-67fa8dcf4530@dewberryfields.co.uk>,
Michael Howard <mike@dewberryfields.co.uk> wrote:
[Snippy]
> They should be two different commands on two lines. But, if your Windows
> installation is not on your 'D' drive, then to make typing easier (the
> results of your commands more visible), first select your 'D' drive. So,
> three commands in total, as follows, in a Windows 'command prompt'
> window;
> D:
> cd D:\ROStuff\V-RPCEmuROD\hostfs
> mklink /D share D:\
> Thats the three commands. The first 'D:' selects your 'D' Drive. The
> second changes directory. The third creates the link. In the third
> command, the '/D' has nothing to do with D Drive, it means create a
> directory link and 'share' could be any legal name of your choice.
> Michael Howard.
Aha! that's much clearer, and I now have the sym links in place and
working, including one for memory sticks.
Thanks Michael, much appreciated. :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Michael Howard <mike@dewberryfields.co.uk> wrote:
[Snippy]
> They should be two different commands on two lines. But, if your Windows
> installation is not on your 'D' drive, then to make typing easier (the
> results of your commands more visible), first select your 'D' drive. So,
> three commands in total, as follows, in a Windows 'command prompt'
> window;
> D:
> cd D:\ROStuff\V-RPCEmuROD\hostfs
> mklink /D share D:\
> Thats the three commands. The first 'D:' selects your 'D' Drive. The
> second changes directory. The third creates the link. In the third
> command, the '/D' has nothing to do with D Drive, it means create a
> directory link and 'share' could be any legal name of your choice.
> Michael Howard.
Aha! that's much clearer, and I now have the sym links in place and
working, including one for memory sticks.
Thanks Michael, much appreciated. :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Friday, 12 January 2024
Re: [Rpcemu] Message meaning
On 12/01/2024 20:04, Dave wrote:
> In article <475885cd-a514-8086-35f6-283b6ced78ad@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 19:17, Dave wrote:
>>> In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
>>> Michael Howard <mike@dewberryfields.co.uk> wrote:
>>>> On 10/01/2024 11:22,
>>> [Snip]
>>>
>>>> I assume you are running RPCEmu on Widows 10? I assume this as you
>>>> are trying to connect to other disks on the 'Host' machine and have
>>>> enabled SMB client support. The other option would be Junctions
>>>> (symbolic links) in you HostFS directory pointing to the folder on
>>>> another drive that you want access to from RISC OS. So, in Windows
>>>> command prompt, change directory to your HostFS directory on the
>>>> host, say; cd c:\users\Dave\rpcemu\HostFS mklink /D share1
>>>> D:\real_dir1 mklink /D share2 E:\dir\real_dir2 This will create links
>>>> named share1 & share2 which you can access from within your HostFS
>>>> root inside RISC OS. D:\real_dir1 & E:\dir\real_dir2 are existing
>>>> directories on two different drives that you want access to. They do
>>>> NOT need to be shared, no need for SMB or LM.
>>> Mmnn!
>>> Accessing a single directory on a drive won't work for me, as per LM98 I
>>> need access to the whole drive in a filer window.
>>>
>>> Thanks for the thoughts anyway. :-)
>>>
>>> Dave
>>>
>> Er,
>> mklink /D share D:\
>> mklink /D share2 E:\
>> etc, etc, etc .....
>> :-)
> I've been busy, so only just got back to this RPCEmu problem...
>
> The path to my RPCEmu...
>
> CD D:\ROStuff\V-RPCEmuROD\hostfs mklink /D share D:\
>
> Does not make "share" link inside the HostFS.
>
> I obviously don't understand...
>
> Dave
>
They should be two different commands on two lines. But, if your Windows
installation is not on your 'D' drive, then to make typing easier (the
results of your commands more visible), first select your 'D' drive. So,
three commands in total, as follows, in a Windows 'command prompt' window;
D:
cd D:\ROStuff\V-RPCEmuROD\hostfs
mklink /D share D:\
Thats the three commands. The first 'D:' selects your 'D' Drive. The
second changes directory. The third creates the link. In the third
command, the '/D' has nothing to do with D Drive, it means create a
directory link and 'share' could be any legal name of your choice.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> In article <475885cd-a514-8086-35f6-283b6ced78ad@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 19:17, Dave wrote:
>>> In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
>>> Michael Howard <mike@dewberryfields.co.uk> wrote:
>>>> On 10/01/2024 11:22,
>>> [Snip]
>>>
>>>> I assume you are running RPCEmu on Widows 10? I assume this as you
>>>> are trying to connect to other disks on the 'Host' machine and have
>>>> enabled SMB client support. The other option would be Junctions
>>>> (symbolic links) in you HostFS directory pointing to the folder on
>>>> another drive that you want access to from RISC OS. So, in Windows
>>>> command prompt, change directory to your HostFS directory on the
>>>> host, say; cd c:\users\Dave\rpcemu\HostFS mklink /D share1
>>>> D:\real_dir1 mklink /D share2 E:\dir\real_dir2 This will create links
>>>> named share1 & share2 which you can access from within your HostFS
>>>> root inside RISC OS. D:\real_dir1 & E:\dir\real_dir2 are existing
>>>> directories on two different drives that you want access to. They do
>>>> NOT need to be shared, no need for SMB or LM.
>>> Mmnn!
>>> Accessing a single directory on a drive won't work for me, as per LM98 I
>>> need access to the whole drive in a filer window.
>>>
>>> Thanks for the thoughts anyway. :-)
>>>
>>> Dave
>>>
>> Er,
>> mklink /D share D:\
>> mklink /D share2 E:\
>> etc, etc, etc .....
>> :-)
> I've been busy, so only just got back to this RPCEmu problem...
>
> The path to my RPCEmu...
>
> CD D:\ROStuff\V-RPCEmuROD\hostfs mklink /D share D:\
>
> Does not make "share" link inside the HostFS.
>
> I obviously don't understand...
>
> Dave
>
They should be two different commands on two lines. But, if your Windows
installation is not on your 'D' drive, then to make typing easier (the
results of your commands more visible), first select your 'D' drive. So,
three commands in total, as follows, in a Windows 'command prompt' window;
D:
cd D:\ROStuff\V-RPCEmuROD\hostfs
mklink /D share D:\
Thats the three commands. The first 'D:' selects your 'D' Drive. The
second changes directory. The third creates the link. In the third
command, the '/D' has nothing to do with D Drive, it means create a
directory link and 'share' could be any legal name of your choice.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Message meaning
In article <475885cd-a514-8086-35f6-283b6ced78ad@dewberryfields.co.uk>,
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 19:17, Dave wrote:
> > In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
> > Michael Howard <mike@dewberryfields.co.uk> wrote:
> >> On 10/01/2024 11:22,
> > [Snip]
> >
> >> I assume you are running RPCEmu on Widows 10? I assume this as you
> >> are trying to connect to other disks on the 'Host' machine and have
> >> enabled SMB client support. The other option would be Junctions
> >> (symbolic links) in you HostFS directory pointing to the folder on
> >> another drive that you want access to from RISC OS. So, in Windows
> >> command prompt, change directory to your HostFS directory on the
> >> host, say; cd c:\users\Dave\rpcemu\HostFS mklink /D share1
> >> D:\real_dir1 mklink /D share2 E:\dir\real_dir2 This will create links
> >> named share1 & share2 which you can access from within your HostFS
> >> root inside RISC OS. D:\real_dir1 & E:\dir\real_dir2 are existing
> >> directories on two different drives that you want access to. They do
> >> NOT need to be shared, no need for SMB or LM.
> > Mmnn!
> > Accessing a single directory on a drive won't work for me, as per LM98 I
> > need access to the whole drive in a filer window.
> >
> > Thanks for the thoughts anyway. :-)
> >
> > Dave
> >
> Er,
> mklink /D share D:\
> mklink /D share2 E:\
> etc, etc, etc .....
> :-)
I've been busy, so only just got back to this RPCEmu problem...
The path to my RPCEmu...
CD D:\ROStuff\V-RPCEmuROD\hostfs mklink /D share D:\
Does not make "share" link inside the HostFS.
I obviously don't understand...
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 19:17, Dave wrote:
> > In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
> > Michael Howard <mike@dewberryfields.co.uk> wrote:
> >> On 10/01/2024 11:22,
> > [Snip]
> >
> >> I assume you are running RPCEmu on Widows 10? I assume this as you
> >> are trying to connect to other disks on the 'Host' machine and have
> >> enabled SMB client support. The other option would be Junctions
> >> (symbolic links) in you HostFS directory pointing to the folder on
> >> another drive that you want access to from RISC OS. So, in Windows
> >> command prompt, change directory to your HostFS directory on the
> >> host, say; cd c:\users\Dave\rpcemu\HostFS mklink /D share1
> >> D:\real_dir1 mklink /D share2 E:\dir\real_dir2 This will create links
> >> named share1 & share2 which you can access from within your HostFS
> >> root inside RISC OS. D:\real_dir1 & E:\dir\real_dir2 are existing
> >> directories on two different drives that you want access to. They do
> >> NOT need to be shared, no need for SMB or LM.
> > Mmnn!
> > Accessing a single directory on a drive won't work for me, as per LM98 I
> > need access to the whole drive in a filer window.
> >
> > Thanks for the thoughts anyway. :-)
> >
> > Dave
> >
> Er,
> mklink /D share D:\
> mklink /D share2 E:\
> etc, etc, etc .....
> :-)
I've been busy, so only just got back to this RPCEmu problem...
The path to my RPCEmu...
CD D:\ROStuff\V-RPCEmuROD\hostfs mklink /D share D:\
Does not make "share" link inside the HostFS.
I obviously don't understand...
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[netsurf-dev] Re: Mailing list host change
On 12/01/2024 19:44, John-Mark Bell wrote:
> On 12/01/2024 19:33, Daniel Silverstone wrote:
>> Hi Everyone,
>>
>> Assuming this email reaches you, then our migration to a new mailing
>> list host has worked.
>
> I have received both so, yes, I believe the migration has worked. I've
> just tweaked the configuration for *this* list (-dev) to disable the
> reply-to override. If it sticks, I'll do the same for -users (and change
> -commits to reply-to here).
It did, so I have!
J.
> On 12/01/2024 19:33, Daniel Silverstone wrote:
>> Hi Everyone,
>>
>> Assuming this email reaches you, then our migration to a new mailing
>> list host has worked.
>
> I have received both so, yes, I believe the migration has worked. I've
> just tweaked the configuration for *this* list (-dev) to disable the
> reply-to override. If it sticks, I'll do the same for -users (and change
> -commits to reply-to here).
It did, so I have!
J.
[netsurf-dev] Re: Mailing list host change
On 12/01/2024 19:33, Daniel Silverstone wrote:
> Hi Everyone,
>
> Assuming this email reaches you, then our migration to a new mailing
> list host has worked.
I have received both so, yes, I believe the migration has worked. I've
just tweaked the configuration for *this* list (-dev) to disable the
reply-to override. If it sticks, I'll do the same for -users (and change
-commits to reply-to here).
J.
> Hi Everyone,
>
> Assuming this email reaches you, then our migration to a new mailing
> list host has worked.
I have received both so, yes, I believe the migration has worked. I've
just tweaked the configuration for *this* list (-dev) to disable the
reply-to override. If it sticks, I'll do the same for -users (and change
-commits to reply-to here).
J.
[netsurf-dev] Mailing list host change
Hi Everyone,
Assuming this email reaches you, then our migration to a new mailing
list host has worked.
We are now hosted on freelists.org. Hopefully things went smoothly and
nobody has to change anything, however if you filtered on list-id
before, then you may have to adjust that filtering; and if you used
digest mode then you will need to log into the freelists.org interface
and fix that up.
Please let me know **directly** if you're having any problems - let's
not flood the list with problems please.
I hope that we'll have the archives migrated soon too, but for now
they're missing.
Regards,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
Assuming this email reaches you, then our migration to a new mailing
list host has worked.
We are now hosted on freelists.org. Hopefully things went smoothly and
nobody has to change anything, however if you filtered on list-id
before, then you may have to adjust that filtering; and if you used
digest mode then you will need to log into the freelists.org interface
and fix that up.
Please let me know **directly** if you're having any problems - let's
not flood the list with problems please.
I hope that we'll have the archives migrated soon too, but for now
they're missing.
Regards,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
[netsurf-users] Mailing list host change
Hi Everyone,
Assuming this email reaches you, then our migration to a new mailing
list host has worked.
We are now hosted on freelists.org. Hopefully things went smoothly and
nobody has to change anything, however if you filtered on list-id
before, then you may have to adjust that filtering; and if you used
digest mode then you will need to log into the freelists.org interface
and fix that up.
Please let me know **directly** if you're having any problems - let's
not flood the list with problems please.
I hope that we'll have the archives migrated soon too, but for now
they're missing.
Regards,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
Assuming this email reaches you, then our migration to a new mailing
list host has worked.
We are now hosted on freelists.org. Hopefully things went smoothly and
nobody has to change anything, however if you filtered on list-id
before, then you may have to adjust that filtering; and if you used
digest mode then you will need to log into the freelists.org interface
and fix that up.
Please let me know **directly** if you're having any problems - let's
not flood the list with problems please.
I hope that we'll have the archives migrated soon too, but for now
they're missing.
Regards,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
Wednesday, 10 January 2024
Re: [Rpcemu] Message meaning
On 10/01/2024 19:17, Dave wrote:
> In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 11:22,
> [Snip]
>
>> I assume you are running RPCEmu on Widows 10? I assume this as you are
>> trying to connect to other disks on the 'Host' machine and have enabled
>> SMB client support.
>> The other option would be Junctions (symbolic links) in you HostFS
>> directory pointing to the folder on another drive that you want access
>> to from RISC OS. So, in Windows command prompt, change directory to your
>> HostFS directory on the host, say;
>> cd c:\users\Dave\rpcemu\HostFS mklink /D share1 D:\real_dir1 mklink /D
>> share2 E:\dir\real_dir2
>> This will create links named share1 & share2 which you can access from
>> within your HostFS root inside RISC OS.
>> D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
>> different drives that you want access to. They do NOT need to be shared,
>> no need for SMB or LM.
> Mmnn!
> Accessing a single directory on a drive won't work for me, as per LM98 I
> need access to the whole drive in a filer window.
>
> Thanks for the thoughts anyway. :-)
>
> Dave
>
Er,
mklink /D share D:\
mklink /D share2 E:\
etc, etc, etc .....
:-)
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 11:22,
> [Snip]
>
>> I assume you are running RPCEmu on Widows 10? I assume this as you are
>> trying to connect to other disks on the 'Host' machine and have enabled
>> SMB client support.
>> The other option would be Junctions (symbolic links) in you HostFS
>> directory pointing to the folder on another drive that you want access
>> to from RISC OS. So, in Windows command prompt, change directory to your
>> HostFS directory on the host, say;
>> cd c:\users\Dave\rpcemu\HostFS mklink /D share1 D:\real_dir1 mklink /D
>> share2 E:\dir\real_dir2
>> This will create links named share1 & share2 which you can access from
>> within your HostFS root inside RISC OS.
>> D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
>> different drives that you want access to. They do NOT need to be shared,
>> no need for SMB or LM.
> Mmnn!
> Accessing a single directory on a drive won't work for me, as per LM98 I
> need access to the whole drive in a filer window.
>
> Thanks for the thoughts anyway. :-)
>
> Dave
>
Er,
mklink /D share D:\
mklink /D share2 E:\
etc, etc, etc .....
:-)
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Message meaning
In article <3cdf4a2b-7677-f0a2-9894-95ff6aeed16a@dewberryfields.co.uk>,
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 11:22,
[Snip]
> >
> I assume you are running RPCEmu on Widows 10? I assume this as you are
> trying to connect to other disks on the 'Host' machine and have enabled
> SMB client support.
> The other option would be Junctions (symbolic links) in you HostFS
> directory pointing to the folder on another drive that you want access
> to from RISC OS. So, in Windows command prompt, change directory to your
> HostFS directory on the host, say;
> cd c:\users\Dave\rpcemu\HostFS mklink /D share1 D:\real_dir1 mklink /D
> share2 E:\dir\real_dir2
> This will create links named share1 & share2 which you can access from
> within your HostFS root inside RISC OS.
> D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
> different drives that you want access to. They do NOT need to be shared,
> no need for SMB or LM.
Mmnn!
Accessing a single directory on a drive won't work for me, as per LM98 I
need access to the whole drive in a filer window.
Thanks for the thoughts anyway. :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 11:22,
[Snip]
> >
> I assume you are running RPCEmu on Widows 10? I assume this as you are
> trying to connect to other disks on the 'Host' machine and have enabled
> SMB client support.
> The other option would be Junctions (symbolic links) in you HostFS
> directory pointing to the folder on another drive that you want access
> to from RISC OS. So, in Windows command prompt, change directory to your
> HostFS directory on the host, say;
> cd c:\users\Dave\rpcemu\HostFS mklink /D share1 D:\real_dir1 mklink /D
> share2 E:\dir\real_dir2
> This will create links named share1 & share2 which you can access from
> within your HostFS root inside RISC OS.
> D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
> different drives that you want access to. They do NOT need to be shared,
> no need for SMB or LM.
Mmnn!
Accessing a single directory on a drive won't work for me, as per LM98 I
need access to the whole drive in a filer window.
Thanks for the thoughts anyway. :-)
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Message meaning
On 10/01/2024 11:22, Dave wrote:
> In article <384fd019-ed1b-9722-646d-82592d66b214@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 07:51, Dave wrote:
>>> RPCEmu 0.9.4 Running RISC OS 5.29
>>>
>>> RPCEmu is network configured and connects okay with Netsurf.
>>> Trying to use LM98 to connect to the other hardrives on the Host
>>> machine.
>>>
>>> Please, what does the following mean?
>>>
>>> 07:22:13.72 ** WimpError ** from LanMan98 Filer Error : &00000000
>>> Message: Insufficient server memory to perform the requested
>>> function.
>>>
>>>
>>> Thanks
>>> Dave
>>>
>> Were you actually carrying out some filer action whilst connected? I ask
>> because I got a similar error the other day whilst creating a very large
>> zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
>> issue.
> Not that I know off, I'd just run RPCEmu and tried to LM98 connect to one
> of the Host Hardrives (The HD is set Win side as Shared.)
>
> Just tried it again. straight from booting, no change.
>
>> As to accessing other drives on the host, you could try using
>> 'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
>> your Hostfs directory.
> Sorry, I think I don't understand that...
>
> Could you expand a bit, please?
>
> Thanks
> Dave
>
> Nb: FWIW. I've checked that in Windows 10, SMB 1.0/cfs Sharing support,
> both Client and Server are ticked On.
>
I assume you are running RPCEmu on Widows 10? I assume this as you are
trying to connect to other disks on the 'Host' machine and have enabled
SMB client support.
The other option would be Junctions (symbolic links) in you HostFS
directory pointing to the folder on another drive that you want access
to from RISC OS. So, in Windows command prompt, change directory to your
HostFS directory on the host, say;
cd c:\users\Dave\rpcemu\HostFS
mklink /D share1 D:\real_dir1
mklink /D share2 E:\dir\real_dir2
This will create links named share1 & share2 which you can access from
within your HostFS root inside RISC OS.
D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
different drives that you want access to. They do NOT need to be shared,
no need for SMB or LM.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> In article <384fd019-ed1b-9722-646d-82592d66b214@dewberryfields.co.uk>,
> Michael Howard <mike@dewberryfields.co.uk> wrote:
>> On 10/01/2024 07:51, Dave wrote:
>>> RPCEmu 0.9.4 Running RISC OS 5.29
>>>
>>> RPCEmu is network configured and connects okay with Netsurf.
>>> Trying to use LM98 to connect to the other hardrives on the Host
>>> machine.
>>>
>>> Please, what does the following mean?
>>>
>>> 07:22:13.72 ** WimpError ** from LanMan98 Filer Error : &00000000
>>> Message: Insufficient server memory to perform the requested
>>> function.
>>>
>>>
>>> Thanks
>>> Dave
>>>
>> Were you actually carrying out some filer action whilst connected? I ask
>> because I got a similar error the other day whilst creating a very large
>> zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
>> issue.
> Not that I know off, I'd just run RPCEmu and tried to LM98 connect to one
> of the Host Hardrives (The HD is set Win side as Shared.)
>
> Just tried it again. straight from booting, no change.
>
>> As to accessing other drives on the host, you could try using
>> 'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
>> your Hostfs directory.
> Sorry, I think I don't understand that...
>
> Could you expand a bit, please?
>
> Thanks
> Dave
>
> Nb: FWIW. I've checked that in Windows 10, SMB 1.0/cfs Sharing support,
> both Client and Server are ticked On.
>
I assume you are running RPCEmu on Widows 10? I assume this as you are
trying to connect to other disks on the 'Host' machine and have enabled
SMB client support.
The other option would be Junctions (symbolic links) in you HostFS
directory pointing to the folder on another drive that you want access
to from RISC OS. So, in Windows command prompt, change directory to your
HostFS directory on the host, say;
cd c:\users\Dave\rpcemu\HostFS
mklink /D share1 D:\real_dir1
mklink /D share2 E:\dir\real_dir2
This will create links named share1 & share2 which you can access from
within your HostFS root inside RISC OS.
D:\real_dir1 & E:\dir\real_dir2 are existing directories on two
different drives that you want access to. They do NOT need to be shared,
no need for SMB or LM.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Message meaning
In article <384fd019-ed1b-9722-646d-82592d66b214@dewberryfields.co.uk>,
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 07:51, Dave wrote:
> > RPCEmu 0.9.4 Running RISC OS 5.29
> >
> > RPCEmu is network configured and connects okay with Netsurf.
> > Trying to use LM98 to connect to the other hardrives on the Host
> > machine.
> >
> > Please, what does the following mean?
> >
> > 07:22:13.72 ** WimpError ** from LanMan98 Filer Error : &00000000
> > Message: Insufficient server memory to perform the requested
> > function.
> >
> >
> > Thanks
> > Dave
> >
> Were you actually carrying out some filer action whilst connected? I ask
> because I got a similar error the other day whilst creating a very large
> zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
> issue.
Not that I know off, I'd just run RPCEmu and tried to LM98 connect to one
of the Host Hardrives (The HD is set Win side as Shared.)
Just tried it again. straight from booting, no change.
> As to accessing other drives on the host, you could try using
> 'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
> your Hostfs directory.
Sorry, I think I don't understand that...
Could you expand a bit, please?
Thanks
Dave
Nb: FWIW. I've checked that in Windows 10, SMB 1.0/cfs Sharing support,
both Client and Server are ticked On.
D.
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Michael Howard <mike@dewberryfields.co.uk> wrote:
> On 10/01/2024 07:51, Dave wrote:
> > RPCEmu 0.9.4 Running RISC OS 5.29
> >
> > RPCEmu is network configured and connects okay with Netsurf.
> > Trying to use LM98 to connect to the other hardrives on the Host
> > machine.
> >
> > Please, what does the following mean?
> >
> > 07:22:13.72 ** WimpError ** from LanMan98 Filer Error : &00000000
> > Message: Insufficient server memory to perform the requested
> > function.
> >
> >
> > Thanks
> > Dave
> >
> Were you actually carrying out some filer action whilst connected? I ask
> because I got a similar error the other day whilst creating a very large
> zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
> issue.
Not that I know off, I'd just run RPCEmu and tried to LM98 connect to one
of the Host Hardrives (The HD is set Win side as Shared.)
Just tried it again. straight from booting, no change.
> As to accessing other drives on the host, you could try using
> 'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
> your Hostfs directory.
Sorry, I think I don't understand that...
Could you expand a bit, please?
Thanks
Dave
Nb: FWIW. I've checked that in Windows 10, SMB 1.0/cfs Sharing support,
both Client and Server are ticked On.
D.
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Message meaning
On 10/01/2024 07:51, Dave wrote:
> RPCEmu 0.9.4 Running RISC OS 5.29
>
> RPCEmu is network configured and connects okay with Netsurf.
>
> Trying to use LM98 to connect to the other hardrives on the Host machine.
>
> Please, what does the following mean?
>
> 07:22:13.72 ** WimpError ** from LanMan98 Filer
> Error : &00000000
> Message: Insufficient server memory to perform the requested function.
>
>
> Thanks
> Dave
>
Were you actually carrying out some filer action whilst connected? I ask
because I got a similar error the other day whilst creating a very large
zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
issue.
As to accessing other drives on the host, you could try using
'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
your Hostfs directory.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> RPCEmu 0.9.4 Running RISC OS 5.29
>
> RPCEmu is network configured and connects okay with Netsurf.
>
> Trying to use LM98 to connect to the other hardrives on the Host machine.
>
> Please, what does the following mean?
>
> 07:22:13.72 ** WimpError ** from LanMan98 Filer
> Error : &00000000
> Message: Insufficient server memory to perform the requested function.
>
>
> Thanks
> Dave
>
Were you actually carrying out some filer action whilst connected? I ask
because I got a similar error the other day whilst creating a very large
zip file using sparkfs, but on real hardware, so it may not be an Rpcemu
issue.
As to accessing other drives on the host, you could try using
'Junctions' (as opposed to 'Hard' liks) on the Windows side from within
your Hostfs directory.
--
Michael Howard.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Tuesday, 9 January 2024
[Rpcemu] Message meaning
RPCEmu 0.9.4 Running RISC OS 5.29
RPCEmu is network configured and connects okay with Netsurf.
Trying to use LM98 to connect to the other hardrives on the Host machine.
Please, what does the following mean?
07:22:13.72 ** WimpError ** from LanMan98 Filer
Error : &00000000
Message: Insufficient server memory to perform the requested function.
Thanks
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
RPCEmu is network configured and connects okay with Netsurf.
Trying to use LM98 to connect to the other hardrives on the Host machine.
Please, what does the following mean?
07:22:13.72 ** WimpError ** from LanMan98 Filer
Error : &00000000
Message: Insufficient server memory to perform the requested function.
Thanks
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Friday, 5 January 2024
Re: NetSurf 3.11 Released
On 28 Dec 2023 as I do recall,
Michael Drake wrote:
> * Options: Added core option to prefer dark mode.
Many thanks - I can't find this (where is it?)
It's not that I actually *want* to use 'dark mode', but I was just
curious about what it looked like....
--
Harriet Bazley == Loyaulte me lie ==
A poor workman blames his tools.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Michael Drake wrote:
> * Options: Added core option to prefer dark mode.
Many thanks - I can't find this (where is it?)
It's not that I actually *want* to use 'dark mode', but I was just
curious about what it looked like....
--
Harriet Bazley == Loyaulte me lie ==
A poor workman blames his tools.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
NetSurf systems migrations
Hi everyone,
We are in the process of migrating various NetSurf infrastructure to new
servers. This may entail the various websites going down momentarily,
and eventually it will entail the mailing list moving to a new server.
We will do our best to make sure that things go as smoothly as possible,
however please bear with us through this transition.
We will let you all know once things should be "back to normal".
Thanks,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
We are in the process of migrating various NetSurf infrastructure to new
servers. This may entail the various websites going down momentarily,
and eventually it will entail the mailing list moving to a new server.
We will do our best to make sure that things go as smoothly as possible,
however please bear with us through this transition.
We will let you all know once things should be "back to normal".
Thanks,
Daniel.
--
Daniel Silverstone http://www.digital-scurf.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Monday, 1 January 2024
Re: Atari build
Hi Vido,
Thanks for confirming that it works on faster hardware. In Netsurf I tried charging the curl parameter in the choices file to no effect.
I don't have Aranym. I last tried to use it about 10 years ago, couldn't get networking to work. Then I was told that the version on the Aranym website was very old. I gave up at that point.
Peter
On 1 Jan 2024, at 00:00, netsurf-users-request@netsurf-browser.org wrote:
Date: Sun, 31 Dec 2023 13:38:23 +0100
From: Uros Vidovic <vidovic.uros@gmail.com>
Subject: Re: Atari build
To: netsurf-users@netsurf-browser.org
About Atari release.
Latest nightly build works normally on the FireBee browsing https pages
included. It takes some time but it renders them nicely!
So I guess the problem with Atari 68060@60MHz is that it timeouts as it is
too slow. @Peter, maybe you can try it in Aranym how NetSurf is working?
As the GUI for Atari builds is not updated can someone point me to the
description of the options in choices fill so we can edit it with a text
editor?
I would like to know mostly how to enable/disable javascript and CSS
rendering? I believe those two options would make page rendering faster.
Vido
Subscribe to:
Posts (Atom)