similar to: read.xport bug of foreign pkg (PR#933)

Afternoon folks: I'm getting a program crash when I try to run demo(rgl). The following error details result: RGUI caused a stack fault in module NVOPENGL.DLL at 017f:695280f0. Registers: EAX=00000002 CS=017f EIP=695280f0 EFLGS=00010246 EBX=00000001 SS=0187 ESP=00572000 EBP=004d1208 ECX=042f1f01 DS=0187 ESI=004d1208 FS=5d1f EDX=00442d84 ES=0187 EDI=042f1f3c GS=5d0e Bytes at CS:EIP: 53 56 8b

Full_Name: Scot McNary Version: 1.7 OS: Windows 98se Submission from: (NULL) (134.192.131.246) Hi, Rgui causes a page fault when asking for lattice graphics after setting par(ask=TRUE). This doesn't happen in 1.6.2, but does in 1.7.0. library(lattice) par(ask=TRUE) example(dotplot) Windows "Details" about crash: RGUI caused an invalid page fault in module R.DLL at

I installed samba as an AD as described on the wiki and set up replication as described on the wiki. I checked and users are not replicated. I am getting the following messages Primary server (SambaCK): LOG: Copyright Andrew Tridgell and the Samba Team 1992-2013 [2013/08/12 08:48:46.359901, 0] ../source4/smbd/server.c:492(binary_smbd_main) samba: using 'standard' process model

Under platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 6.1 year 2002 month 11 day 01 language R and using foreign 0.5-8 I am encountering errors when using read.xport. Here's

Hi, I'm experiencing a strange issue while attempting to import some XPORT formatted datasets created using SAS 9.3. I 'm using R 2.2.1 with a recently downloaded version of the "foreign" package, although I don't have the version for that handy. I have been able to load some of the XPORT datasets, however when I increase to the entire dataset, I get the following error:

I installed the foreign library yesterday, and have successfully used the read.xport() function to get data from SAS. This is very helpful. SAS "date" and "datetime" variables become numeric variables, which is, of course, what they really are in SAS. Naturally, it is desirable to convert them to date/time objects in R. Looking at the documentation for the SAS transport

Hi All, is there a way of directly writing to disk file, the dataframe or list of dataframes that result from read.xport function. This function converts SAS export files to R dataframes. I would like to convert a SAS transport file to R, but the resulting R dataframes do not fit in the memory of my computer. Is there way to write the output of this fucntion to disk, perhaps using some pipe or

I get a segfault when trying to read a SAS transport file with rather long rows using read.xport from package foreign (version 0.4-7). The culprit seems to be these lines in xport_read in SASxport.c: 590 } else { 591 c = strchr(tmpchar, ' '); 592 *c = '\0'; 593

I see in the archives significant discussion about SAS, CDISC formats etc. for FDA, but no direct suggestion of adding a write.xport method to the foreign package. Are there significant barriers to doing so? [[alternative HTML version deleted]]

Hi All, In 2005, I noted that when I used read.xport function in the foreign package to import a SAS transport file (.xpt) with multiple files imbedded in it, data frames from some of the files were not created. Since then, I discovered that the information from the missing files is being read into one dataframe, but the data appear corrupted. This has been noted before by Dr. Harrell (in

I have found that data imported from SAS using read.xport() in package foreign (installed recently) does not match the original data, when the data consists of character strings that are only one character long. Here is an example. ---- SAS commands to create the data ---- options nocenter; data foo; a='a'; b='bb'; length c d $2; c='c'; d='

The Details. In the following version. > version _ platform i386-pc-linux-gnu arch i386 os linux-gnu system i386, linux-gnu status major 1 minor 8.1 year 2003 month 11 day 21 language R > lookup.xport ignores some datasets in sas export file. File "emptySasData3.xpt" (available at http://biostat.mc.vanderbilt.edu/tmp/emptySasData3.xpt) is a

We are trying to read a sas export file into R. (Works fine on Mac by ftping the export file from solaris box and then importing to R with read.xport, this gives rational numbers etc.) Trying to do this on an IBM Power p655 running linux, reading the same sas export file as used on MAC, in this case the results are not rational. Many of the numbers are interpreted as INF etc. Is it possible

A colleague pointed out that the United States Food and Drug Administration (FDA) has adopted a transport format defined by SAS Institute as a standard for electronic submissions of data. As a result, this format has been openly documented. The URL for the documentation on the format is http://ftp.sas.com/techsup/download/technote/ts140.html Information on the FDA standards for

Hi All, Sorry that I didn't provide enough information. I've been trying to import SAS xport files that contain multiple files using package foreign's read.xport. I first attempted this back in 2005 and had problems. Some of files that were present in the SAS xport file weren't being created in R. I submitted my problem to the community:

I am trying to import data from a SAS XPORT file that contains 24 SAS files. When I use the "read.xport" procedure only about 16 data frames (components) are created. Any suggestions? ************************************************************************* Gary A. Nelson, Ph.D Massachusetts Division of Marine Fisheries 30 Emerson Avenue Gloucester, MA 01930 Phone: (978)

Full_Name: Ruskin Chow Version: R 2.0.1 OS: Windows 2000 Submission from: (NULL) (203.169.154.66) Data imported from SAS using read.xport() in package foreign are converted to <NA> when the SAS data field consists of character strings that are only one character long. This is apparently a previously reported bug and perhaps fixed in some platform other than Windows (rw2001).Some

I've updated the win32 icecast2 binary on my site to reflect current CVS (as of now - March 19, 2003).... It's available here for anyone interested : http://www.oddsock.org/tools/icecast2/ <p>oddsock <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

This is of course an incorrect usage, which I've trapped at R level, so as to give an informative warning. On Tue, 28 May 2002 NEFTH@pacbell.net wrote: > The following sequence of commands: > graphics.off() > dev.control("inhibit") > > causes R to memory-fault and core dump. This is reported > for a new port of R, but is also reproducible on Windows > and

(1) With MSVCRT.DLL (version 4.20.6164) from ftp://ftp.microsoft.com/softlib/mslfiles/msvcrt.exe installed in rw1051\bin directory, as per RWinFAQ 2.14: RGUI caused an invalid page fault in module MSVCRT.DLL at 017f:78014b90. Registers: EAX=0093007a CS=017f EIP=78014b90 EFLGS=00010246 EBX=017a2360 SS=0187 ESP=0091eee4 EBP=0091ef10 ECX=ffffffb5 DS=0187 ESI=00000000 FS=5bbf EDX=81d7d520 ES=0187