search for: imgres

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: > >

I get the following error at the browser: ArgumentError in ImagesController#upload invalid geometry string `110×'' ... for the call to change_geometry with an explicit size (''110x'') as the geometry string: def make_thumb (the_img) require ''RMagick'' size = "110x" debugger if ENV[''RAILS_ENV''] ==

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

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:

> 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

On Sun, Dec 2, 2018 at 12:32 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > When booting in UEFI x64 mode in your next test, you should see a boot > > > menu. > > > > Nope: > > > > *** Press enter to boot the default label *** > > Failed to load libcom32.c32 > > Failed to load COM32 file SYSLINUX/EFI64/vesamenu.c32 >

> Now it is just dd, mkfs and copy in the files we need. > One less thing to worry about keeping versions consistent. > > > I just noticed those 2 files that were added by > > > syslinux -i boot.img > > > (right?) > > > > > > Yes, those 2 files came from your 'syslinux' command (in your other > > email). We don't want anything

Dear R Users, Do you know of an existing function that allows the production of sensitivity and specificity forest plots? See the following for an example: http://www.google.co.uk/imgres?q=forest+plots+of+sensitivity+and+specificity&um=1&hl=en&authuser=0&biw=1920&bih=989&tbm=isch&tbnid=JLxXNU7iQ2N_CM:&imgrefurl=http://www.medscape.com/viewarticle/717751_3&docid=NnthE8_KgNQZdM&imgurl=http://img.medscape.com/article/717/751/717751-fig3.jpg&...

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

...) colnames(states) <- c("Lon","Lat") ggplot(states, aes(x=Lon, y=Lat)) + geom_path() + geom_point(alpha=0.6,size=0.3,data=subway) # Where I got the code from and also an image of what I am attempting to do (please enter this in your URL) http://www.google.com/imgres?um=1&hl=en&biw=1790&bih=845&tbm=isch&tbnid=4rMjXYA_w1qDiM:&imgrefurl=http://www.informaniac.net/&docid=SJqcsPghztrj0M&imgurl=http://lh5.ggpht.com/_yBbodrC25kU/Ta6Ifqr0ZLI/AAAAAAABRCg/98rIF-kMMns/map%25255B7%25255D.png&w=512&h=319&ei=mgsbUIzqJuKbiAL5v4DQDg...

...: xflags=0x7a l1=255 l2=784 lastname=/home/cpanelBackup/cpbackup/daily/haspixie/homedir/public_html/wp-c ontent/cache/supercache/icanhaspixiedust.com/category/characters-and-stars/m ickey-mouse/http%3A/icanhaspixiedust.com/category/characters-and-stars/micke y-mouse/&r=http%3A/images.google.com/imgres%3Fimgurl%3Dhttp%3A/icanhaspixied ust.wordpress.com/files/2009/04/waltalittlehelp.jpg%26imgrefurl%3Dhttp%3A/ic anhaspixiedust.com/category/characters-and-stars/mickey-mouse/%26usg%3D__x0V i5fm7subadydrHNAEmp0zsgk%3D%26h%3D454%26w%3D600%26sz%3D84%26hl%3Den%26start% 3D117%26um%3D1%26tbnid%3DWqq7BmZ7aN...

> > _ target/EFI/BOOT/SYSLINUX.CFG > > I don't think that exists? (see list below) In our "first test" (simple boot prompt), we created "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ "target/EFI/BOOT/SYSLINUX/EFI64/SYSLX64.CFG". Part of my intention was to test whether it actually reaches one cfg or the other.

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: config prompt.cfg prompt.cfg does not exist, but I would expect similar behaviour between efi and legacy. test is: starting with blank image, mkfs, mount it... + cp

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???