Displaying 6 results from an estimated 6 matches for "catlabels".
Did you mean:
catlabel
2007 Aug 07
0
warning in library(GRASS)
...maps (12) read from the GRASS GIS.
But for every map and loop I always use RGRASS.temp as the R-workspace
name for the imported raster files, no matter the name of the source
GRASS raster map, e.g;
RGRASS.temp <-
rast.get(G,rlist=paste(A2.grassname,it,".Bmaxind.",ib,sep=""),catlabels=FALSE)
As I always overwrite the same R object, I should hope that the number
of calls to rast.get would have no influence on a warning like "Too many
open raster files", which I'm getting after the fourth loop.
Am I missinterpreting something about the way R objects are stored,...
2018 Dec 07
0
efi config hang
First, I'm confused. In the prior "whole" setup (the one you generated
after my 15 steps, plus one workaround), was/is the basic boot menu at
least "working" when you used the workaround for the buggy PATH
directive when booting in UEFI mode? I mean:
"PATH EFI/BOOT/SYSLINUX/EFI64/"
in
"target/EFI/BOOT/SYSLX64.CFG".
It is not perfect, but at
2018 Dec 07
2
efi config hang
On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
>
> First, I'm confused. In the prior "whole" setup (the one you generated
> after my 15 steps, plus one workaround), was/is the basic boot menu at
> least "working" when you used the workaround for the buggy PATH
> directive when booting in UEFI mode? I mean:
>
>
2018 Dec 07
2
efi config hang
On Thu, Dec 6, 2018 at 5:14 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
>
>
> > works with legacy, hangs with efi.
> >
> > where works is:
> > No DEFAULT or UI configuration directive found!
> > but enter and ^v make things happen
> >
> > hangs is: nothing happens, no response from keyboard, have to reboot.
> >
> > note:
2018 Dec 07
0
efi config hang
> On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
> >
> > First, I'm confused. In the prior "whole" setup (the one you generated
> > after my 15 steps, plus one workaround), was/is the basic boot menu at
> > least "working" when you used the workaround for the buggy PATH
> > directive when booting in
2018 Dec 07
2
efi config hang
On Fri, Dec 7, 2018 at 7:47 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
>
>
> > On Thu, Dec 6, 2018 at 10:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote:
> > >
> > > First, I'm confused. In the prior "whole" setup (the one you generated
> > > after my 15 steps, plus one workaround), was/is the basic boot menu at