similar to: Memory allocation error: failed to expand to 1108555744 bytes

I'm trying to move some roaming profiles from Domain A to B. All of the profiles are from XP SP3. The originating machine is Debian 5/AMD64, samba 3.4.5 from Debian packages. The destination machine is Ubuntu 9.10, but x86. From everything I've read and found online, `profiles` is supposed to work for XP with no problems. When I attempt to do a SID change on NTUSER.DAT, I get

Hi. Current host OS: CentOS5.9 Current client OS: Windows XP (all the latest stuff) Current Samba: 3.6.6-0.129.el5 Ever since 3.4 I am having problems with the "/usr/bin/profiles" binary, it does NOT allow me to change a SID within a registry file. However, using an older version of the binary (3.0.33-3.29.el5_5.1) it does. If I execute the following command (note the last 4 digits on

Hi. I have just changed to the latest version of samba on a CentOS 5.4 machine as I now have Win7 computers in the domain. [root] #>smbd -V Version 3.5.4-0.83.el5_7.2 On the old version (I think 3.0.29) I was able to change the SID on any NTUDER.DAT file happily. Now I cannot change SID on any NTUSER.DAT file. However, I can log into the domain using the username that is attached to the

Cups 1.2.7 Debian Etch with Samba 3.0.24 Clients: WinXP SP3 (with Firewall completely off for testing) When I define a printer specifically in smb.conf, they show up as shared printers in WinXP. But when I follow the normal way (see below) to load all from cups they don't. I followed mainly the latest SAMBA-HOWTO (chapter 21-22) The only error I see in log.smbd when accessing the

Hi all I have got a samba-3.0.13 (hot off the press) PDC running here that also works as a print server printig via cups-1.1.23. As a backend I use openldap-2.2.11 What I get in my log files is what you see below. It seems this only happens when the user prints a *.pdf file. The message shows up once in a while, definetly not for every print job that gets submitted. Printing of those *.pdf

I need to look more into it, but before I start the long and arduous "googling my life away" process, I figured someone might know the answer. I've read the man pages several times and they didn't change! :-( As normal, while looking at one thing, something else bites my butt. I tuned on the swap field in top and sort on it. Here's an edited snippet of the results. Mem:

hi you, I'm having problem with voice quality on my trixbox using TDM2400B.The trixbox is connected via 20 FXO ports on a TDM2400 with the hardware echo cancel module. Echo cancel almost works, but the users hear what they describe as a 'background crackle/buzz' coming back when they talk. anyone have the same problem? pls help me. thanks a lot. my trixbox and config

Hi all, I have a problem during the lauching of my first virtual image. First thing : domain 0 is on fedora core 6 (probably a xen package made in fedora :-S, sorry ...) Second thing : the error is really traditional (i already had it with uml) but there i am blocking. here my config file (for image on logical volume, swap too) root = "/dev/sda1 ro" [root@p-virtvip8 xen]# cat p-virtser9

Hi all, I''ve upgraded my system to Rails 1.1.1 successfully. After much looking I haven''t found out how to migrate an existing application to a new rails version though. What is the procedure, if any, for upgrading the application I''ve developed in 1.0? Is there a script I need to run? -- Posted via http://www.ruby-forum.com/.

RH9 on intel, with samba-built RH9 samba 3 rpm freshly installed. I have a raw cups printer which samba picks up, but when a client connects (root) and selects the host's "printers" folder, a right click on the printer and properties causes a small delay and then the msgbox: "Printer Properties could not be displayed, operation could not be completed." testparm

The Wine development release 1.1.38 is now available. What's new in this release (see below for details): - Better support for memory allocations debugging. - Improved MIDI support. - A wide range of Direct3D fixes. - OLEDB fixes (should fix Clipart in Office). - Improved debugger support on x86-64. - Many MSI fixes. - Various bug fixes. The source is available from the