similar to: Problems accessing shares on Samba from Win2000

Hi all. I'm brand new to R. My dataset (stored in MySQL) is a list of weather stations in rows by year with various weather variables in columns, for example: STNID YEAR TEMP DEWP station1 1990 54 50 station1 1991 23 10 station1 1992 34 18 station2 1990 45 41 station2 1991 32 25 station2 1992 21 11 I'm trying to run

Looking for general theory here - perhaps this will devolve into more "how to" later, but right now I need overall understanding. We handle DHCP outside AD. We also do DDNS there, and handle DNS lookups. Here's what the current setup looks like We have a pair of DHCP servers (ISC DHCPD) and those same boxes handle DNS for the network. They're in the DNS domain of, lets say;

hello, I have just install the samba soft on a Solaris 2.5 station. For the beginning, I try to print whith a PC Window's 95 configuration on a printer define on my server Samba. In my office, The PC are enable to communicate this a Novell Server. When I try to print with a PC via Samba, it is possible, if in a first time, I connect me on the server Novell (authentification database of

Hi everyone. I have a question about a work on R I have to do for my job. I have temperature data coming from 70 weather stations. One data file corresponds to one station for one year (so 70 files for one year). Each file looks like this (important: each file contains NAs): time data 01/01/2008 00:00 -0.25 01/01/2008 00:15 -0.18 01/01/2008 00:30 -0.25 01/01/2008

(As a noob to R, this is my first posting - yes yes, groans all around...) I'm trying to extract certain rows from a data frame. I used the following to import data from a CSV txt file. data <- read.table(file="data.txt", header=TRUE) when I do this, my attempt to extract the data rows only from where the Station value equals 1? data.station1 <- data[data$Station == 1]

> Hi, > > > The current states of each of those drives seem to suggest that, with > > those particular values, they would not be ideal for booting > > purposes. > > For me as half-educated user all three would look like > "normal" MS-DOS disks. So people buy pitfalls. The filesystem might be OK, but not ideal for a broad compatibility for booting

As I said before, booting is bigger than one bootloader. I am replying to what I think was asked. I might have misunderstood the questions. Whichever the case, this email is less about Syslinux itself. If this is considered too far off-topic in the Syslinux Mailing List, please receive my apologies. > > I still have the factory-set contents of my three USB sticks. A small

On 01/21/2014 12:22 AM, Thomas Schmitt wrote: > >> If we take the ENDing CHS values as valid: >> 982 / 254 / 63 >> and we calculate the corresponding LBA: >> ( ( 982 + 1 ) >> x ( 254 + 1 ) >> x ( 63 ) ) >> - 1 >> ___________ >> 15'791'894 > > Is this calculation generally valid ? It seems to assume that > the

Hello! I?ve got trouble to print via Samba. But read to the end to understand: My printer (a Canon BJC 620) is connected to a Win98 box. Its network name is canon. The /etc/printcap entry is: ---/etc/printcap--- lp|smb|canon:\ :cm=unser Drucker:\ :sd=/var/spool/lpd/smb:\ :af=/var/spool/lpd/smb/acct:\ :if=/usr/local/samba/bin/smbprint:\ :mx=0:\

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

Dear users, I have monthly station data (44) stations data for 45 years which I have read in R using read.table. the data is in the format: Year Month Station1 Station2 ...................................... Station 44 (i.e the column names in the 1st row), I also have the latitude and longitude of the stations in a separate file in R (in the format : Station LAT LON). I wish to

Hi, Ady wrote: > I personally don't like this "hiding" [of CHS], but I understand > their reasons to do so. > > I think that the "USB-Geometry" section in the wiki should try to > point to the same kind of users. But it is in wiki page Hardware_Compatibility. Check out the neighborhood. If there is a place to - for once - state how a "normal"

Hello, (please excuse poor translations of german Windows-GUI-items) a customer of ours has a strange problem trying to install a printer driver on the print$ share. The driver in question comes from http://www.kyocera.de/kyocera_n/german/downloads/downloads.html -> choose 'Treiber' -> choose 'Produkt Typ: Drucker', choose 'Produkt: FS-6020', choose 'Sprache:

the closest i have gotten to a consistent way to test a MS-DOS filesystem setup is: dd if=/dev/zero of=binary.img bs=1M count=500 i="$(losetup -f --show binary.img )" parted binary.img mklabel msdos -s -m dd if=/usr/lib/syslinux/mbr.bin of="${i}" parted binary.img mkpart primary -a optimal -s -m 0% 100% parted binary.img set 1 boot on mkfs.ext4 $(kpartx -savu "${i}"

Op 2013-12-15 om 17:39 schreef Ferenc Wagner: > Ruben Kerkhof <ruben at rubenkerkhof.com> writes: > > > /* 80 00 00 00 ee 00 00 00 > > - - bootable partition, type EFI (EE), no CHS information */ > > + - bootable partition, type EFI (ED), no CHS information */ > > Please fix the previous comment line as well. As I understand that, so in _my words_:

Hi, Ady wrote: > If a specific BIOS' CHS/LBA translations cannot cope with the above, it > is no surprise that we get some mess, somewhere. Currently my suspicion is that the isohdpfx.S code simply mishandles the two conversion factors which it correctly got from BIOS call INT 13H AH 8. > Boot System ID : First : Last : Relative : Number of: > Flag

On 01/21/2014 11:13 AM, Thomas Schmitt wrote: > > My current theory is that vendors prefer to record > a cylinder aligned end CHS address over recording > an end CHS address which exploits the whole capacity. > This is used as an (inofficial ?) protocol to publish > the CHS factors H' and S'. > Indeed it is -- at least some BIOSes "deduce" the H/S to use

The handover protocol uses ED as partition type but the comment above it still mentions EE Signed-off-by: Ruben Kerkhof <ruben at rubenkerkhof.com> --- mbr/gptmbr.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mbr/gptmbr.S b/mbr/gptmbr.S index 7f450d3..8ab6b50 100644 --- a/mbr/gptmbr.S +++ b/mbr/gptmbr.S @@ -194,7 +194,7 @@ found_part: pushw %di /* 80 00 00 00

One solution is to change the order of your DNS server: your PC's DNS points to AD, and AD forwards queries to your bind server. But I don't this: how do you deal with the DDNS and the ip change of AD? Otherwise just use static IP for your station1 or server. Allen You have to be careful with this.... 1. DNS order is NOT guaranteed....,ESP. with caching.. some OS very helpfully added

On 10/13/2010 08:36 AM, syslinux-bot for Michal Soltys wrote: > Commit-ID: 9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Gitweb: http://syslinux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Author: Michal Soltys <soltys at ziu.info> > AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200 > Committer: Michal Soltys <soltys at ziu.info> > CommitDate: Wed, 13