Displaying 20 results from an estimated 306 matches for "1.75".
Did you mean:
1,75
2000 Mar 01
0
isoMDS error message!!! (fwd)
uhps!!
I forgot to tell you that I'm running R 0.99.0 for windows32 on windows 95
osr2.
Thank you very much for the latest R-1.0.0 (even if I don't tried it
yet)!!!
Andrea Rossetti
University of Perugia (Italy)
Statistical Science Department.
---------- Forwarded message ----------
Date: Tue, 29 Feb 2000 17:03:51 +0100 (MET)
From: Andrea Rossetti <rossetti at markov.stat.unipg.it>
2002 Jun 14
0
SYSLINUX 1.75-pre7 released - FINAL 1.75-pre
I have just released SYSLINUX 1.75-pre7. Barring any showstopper bugs,
this WILL be the final 1.75, so please test if out, and if you find
problems speak now or forever hold your pizza.
After 1.75 is out I'm going to be spending most of my time on the new
2.00 release.
http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/
-hpa
2017 Oct 05
4
dealing with a messy dataset
dear R-users,
I am facing a quite regular and basic problem when it comes to dealing
with datasets, but I cannot find any satisfying answer so far.
I have a messy dataset of galaxies like that :
And XVIII 000214.5+450520 0.69 17 9 0.00 -8.7 26.8 6.44
6.78 < 6.65 -44 0.5 MESSIER031 0.6 1.54
PAndAS-03 000356.4+405319 0.10 17 0.00 -3.6 27.8
4.38
2002 Jun 15
2
Bug in 1.75 PXE code
Hi!
I've spent the last days trying to get PXE working (with all the nice
stuff that's in the specification - doesn't work :-( )
So I tried the new 1.75 with the Intel DOSUndi Bootdisk (which should
verify that everything works correctly) but it does no longer work
with syslinux-1.75!
1.74 is fine - so I guess something is broken here ...
Please have a look at it - and let me know
2008 Jan 07
1
Avoiding FOR loops
useR's,
I would like to know if there is a way to avoid using FOR loops to perform
the below calculation.
Consider the following data:
> x
[,1] [,2] [,3]
[1,] 4 11 1
[2,] 1 9 2
[3,] 7 3 3
[4,] 3 6 4
[5,] 6 8 5
> xk
Var1 Var2 Var3
1 -0.25 1.75 0.5
2 0.75 1.75 0.5
3 1.75 1.75 0.5
4 2.75 1.75 0.5
5 3.75 1.75
2017 Oct 05
0
dealing with a messy dataset
It looks like fixed width. I just used the last position of each
field to get the size and used the 'readr' package;
> input <- "And XVIII 000214.5+450520 0.69 17 9 0.00
-8.7 26.8 6.44 6.78 < 6.65 -44 0.5 MESSIER031 0.6
1.54
+ PAndAS-03 000356.4+405319 0.10 17 0.00 -3.6 27.8
4.38 2.8 MESSIER031
2002 Jul 11
1
help with porting patch from 1.62 to 1.75
Hello List,
I have below a patch (against Syslinux-1.62), which adds
a pseudo-kernel 'swap' which swaps device numbers of
the boot device and the first harddisk. It was made
for a system equipped with a DiskOnChip (www.msys.com)
device which 'steals' the device# of teh first harddisk,
This patch is used to enable the syslinux on the DoC
to continue booting from the harddisk as if
2002 Jun 15
0
SYSLINUX 1.75 released
I have released SYSLINUX 1.75 -- this one is identical to 1.75-pre9
except the version number. I have gotten enough testing done that I
feel it's time to release...
Changes in 1.75:
* ALL: NASM 0.98.32 or later is now required to build
SYSLINUX from sources.
* SYSLINUX: put back in the workaround for the BIOS floppy
table. This seems to be a
2008 Jan 08
1
using lapply()
useR's,
I am trying to find a quick way to change some values in a list that are
subject to a condition to be NA. Consider the 3x1 matrix:
delta <- matrix(c(2.5,2.5,1), nrow = 1)
And consider the list named v that has 3 elements
> v
v[[1]]
[,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [,9] [,10] [,11] [,12]
[,13] [,14]
[1,] 4.25 3.25 2.25 1.25 0.25 0.75 1.75 2.75 3.75 4.25
2017 Oct 05
3
dealing with a messy dataset
dear Jim,
Thanks for your reply and your proposition.
I forgot to provide the header of the dataframe, here it is:
================================================================================
Byte-by-byte Description of file: lvg_table2.dat
--------------------------------------------------------------------------------
Bytes Format Units Label Explanations
2002 Jun 06
0
SYSLINUX 1.75-pre3 released
http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/
Here is the list of changes in 1.75 so far:
Changes in 1.75:
* ALL: NASM 0.98.32 or later is now required to build
SYSLINUX from sources.
* SYSLINUX: put back in the workaround for the BIOS floppy
table. This seems to be a requirement for "extended" floppy
formats to work
2002 Jun 11
0
SYSLINUX 1.75-pre4 released - RELEASE CANDIDATE
Hi all,
I have released SYSLINUX 1.75-pre4, which is a release candidate for
1.75. Please pretty please test it out:
http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/
I'm working on some new stuff, basically COMBOOT+an API+32-bit support,
which should make doing things like menus and other UI features very
easy as separate modules. When that gets finished I'll probably
2002 Jun 15
0
SYSLINUX 1.75-pre9 released
I have released SYSLINUX 1.75-pre9... it's just a simple one-line bug
fix over -pre8. I expect this will be the final 1.75.
http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/
-hpa
2002 Jun 16
1
Bug in 1.75 PXE code (fwd)
> Marcel Ritter wrote:
> >
> > The good thing about it: The PXE code removal seems to work now ...
> >
> > But I'm not quite sure about the syntax - is the following right?
> >
> > label undi
> > kernel memdisk keeppxe
> > append initrd=UNDITest/dosundi.1
> >
> > The documentation only says:
> >
> > ... option
2002 Jul 03
1
syslinux 1.75
Hi all,
I'm setting up a diskless linux system using pxelinux. I have reached the
point where the kernel boots and init starts. However, I'am getting this
message:
INIT: version 2.78 booting
can't create lock file /etc/mtab~14: Read-only file system (use -n flag to
override)
INIT: Entering runlevel: 2
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more
2004 Apr 30
3
Syslinux 1.75, LEAF Bering 1.2, Compaq 2266
I have been using the LEAF Bering firewall for a year or so. It boots
with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it
formats the diskette as 1680KB. Recently I found a small Compaq 2266 box
to replace a larger Compaq 7170 to run the firewall. But when I try to
boot the Bering diskette on the 2266 I get the following message:
Loading Linux ............
Boot failed:
2017 Oct 05
0
dealing with a messy dataset
Is this a fixed width format?
If so, read.fwf() in base, or read_fwf() in the readr package will solve the problem. You may need to trim trailing spaces though.
B.
> On Oct 5, 2017, at 10:12 AM, jean-philippe <jeanphilippe.fontaine at gssi.infn.it> wrote:
>
> dear R-users,
>
>
> I am facing a quite regular and basic problem when it comes to dealing with datasets,
2001 Feb 21
0
[Announce] pgp4pine-1.75-6 - expired public keys (from: vab@CRYPTNET.NET)
Hi,
Pine user should read the following advisory. I have not checked it
because I don't use Pine.
Werner
--
Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est.
-- Augustinus
-------------- next part --------------
An embedded message was scrubbed...
From: "V. Alex Brennen"
2002 Jun 02
0
SYSLINUX 1.75-pre1 available
Please try this version out if you are using floppies to boot, and
*especially* if you have observed either of the following two problems:
a) "booting with syslinux without -s takes forever"
b) "booting with syslinux without -s doesn't work, -s works"
Changes in 1.75:
* ALL: NASM 0.98.32 or later is now required to build NASM
from sources.
*
2009 Jun 18
1
recovering the name of a given value in a matrix
Hi all,
I've got object *cumsumtab, *where the first row (1,2,3,4,5,6,8,13,14,17,40)
are names (actually, categories), and the second row has numeric values.
> cumsumtab
1 2 3 4 5 6 8 13 14 17 40
2 4 6 7 9 11 13 14 15 16 17
I'm trying to find a way of finding to which category ( in *names(cumsumtab)
* ) belongs a given value (let's say Q1 <- 4.25). So far, I've