similar to: Samba screwed up when trying to save a word97 document

Futher to my last message regarding samba being confused when a Word97 file was being saved. I have been looking at the docs and log files again and now understand that the problem is related to opportunistic locking. I also found the part of the log file that details the start of the event. Here it is: 1998/06/19 15:51:19 ukswi1000 (175.12.50.218) connect to service its as user bramsons

RH7.1, wine release 20010731. There is no windows installed on this computer and I try to install Word97 in 'no-windows' environment'. After I run 'wine setup' I see the initial word installation screen but after entering code numbers I see the following eror messge: Setup error 544: Setup is unamble to open data file E:\MSSETUP.T\~msstfof.t\Word97.stf. Run setup again from

Hallo! Can anybody tell mw how can i install word97 or word 2000 with wine. it does not do anything. when i try wine e:\setup.exe word tell me that some options lost. but when i try insert some options it told me wrong options or not enough options. system rh7.2 codeweaver 200111.. no windows -- See you Michael Ott /----------------------------\ .--. | Michael Ott |

Hello win(n)ers, has someone managed to use word97 with the last release 0.9.10 ? It doesn't work with the 0.9.8 either. The problem is rather tedious, i cannot write/save any document files from word. But it works with notepad ! I get something like, Cannot access folder C:\windows\Profiles ... O course, changing for an other folder doesn't help. Thx Jj

Dear friends: Thanks to Ekkehard, I found out how to launch Word97. I went to the .wine/drive_c directory and then (using quotes around "Program Files" and "Microsoft Office") I cd's to where Winword.exe was and then typed, within this subdirectory: wine WINWORD.EXE. That launched Word97 at last. But when I try to save a document, all I get is the first letter of the file

Hi, I support around 15 Windows 2000 Clients who log into and have home directories on a Samba PDC running under RedHat 7.3. The version of samba I am using is 2.5.5. All the clients use Word97 SR2 and they all get the following error while working on documents stored on their home directories on the PDC: Word failed reading from this file (filename.doc). Please restore the network

I've just installed wine 20011004 using tarball. Wordview and word seem to run nicely, but I cant save edited files. Word claims that the file already exists or that it is RO or that there is not enough memory and/or disk space. Anyone knows a solution to this?? Thanks in advance! - Vode

Hello! I am new to this list (although I have done a fair amount of research in the archives) and I need to ask what is probably one of the most frequently asked questions on a list like this: How do I install Word97 and Excel97? (Codeweavers CrossoverOffice can do this, and they ASSURE us that they roll everything they do back to the main wine CVS and hence, this SHOULD work!) So far; this is

Hello, I (still) have some problems with a printer-driver managed by the spools-system of samba. In short: When I try to open the printer-properties of a Deskjet 1120C in MS-Work 97 the error "Word can not show the properties-dialog, because there was an error during the printing" (translated from the german message) in MS-Word 2000 the properties-dialog shows up, but although I did

Hi, Microsoft word 97 seems to get stuck in a FlashWindow loop. Briefly, the word splash screen and main window come up fine. When I click on the File menu and then on the Open choice, wine seems to get stuck in a loop in which the window title bar flashes active and inactive. A preamble and a couple of loop iterations follow in the trace below. Looping behavior does not occur when I try the

Dear friends: I am using PCLINUXOS version .92. My problem, simply put, is that I cannot SAVE or LOAD documents in MSWord97 using the older Codeweavers Crossover Office Wine 1.3.5. Thinking the problem might be resolved in the latest Crossover Office 5, I downloaded the Tryout version but the same problem occurs (i.e. at least for me) in this latest version. In fact, it wouldn't even

Hey, i build my first Linux Server in Oktober 2001. Everything works fine. At the end of Februar 2002 i got a problem. Please see the logfile. [2002/02/25 09:02:15, 0] smbd/password.c:domain_client_validate(1563) domain_client_validate: could not fetch trust account password for domain NENN [2002/02/25 09:02:47, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response

we are running Samba 2.0.6 on a solaris 7 (intel) box. Users (about 270 at one time) connect to the home directories located on the samba server by NT 4 workstations . Problem is ..Some times they lose access suddenly .In the log files the following message appears ?------- [2000/08/22 08:28:09, 0] smbd/oplock.c:request_oplock_break(1202) request_oplock_break: no response received to oplock

Users are trying to cennect to their home dirs ... the request_oplock_break is failing: [1999/10/21 10:50:39, 1] smbd/service.c:make_connection(521) gpnte109i (137.94.128.183) connect to service s22350 as user s22350 (uid=22350, gid=34) (pid 27704) [1999/10/21 10:50:54, 0] smbd/oplock.c:request_oplock_break(1136) request_oplock_break: no response received to oplock break request to pid 25867

Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks. Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as printservices. Server acts as PDC and WINS server. Clients are W2K SP2 (a few with SP3). There are +/- 100 clients. We see a server that is 100% busy and we see during a long time a very high CPU load (60- 95%) related to one W2K client. When

I've seen a couple mentions of trouble w/ large files in the list archives, but nothing that seems to resolve this problem... When trying to move or copy largish files (~ >1MB) with WinN using Samba 1.9.18p10 on a Sparc Solaris 2.5 system, things hang for a while and then a dialog box pops up saying "Cannot copy {filename}: The session was cancelled. I've tried setting

Hello All, this morning, after rebooting our samba-testserver to activate some patches, we continuously got this error: [1999/02/18 09:53:29, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break request to pid 1650 on port 1230 for dev = ff000009, inode = 53134 [1999/02/18 09:53:40, 0] smbd/oplock.c:(943) request_oplock_break: no response received to oplock break

Hello, I'm running a samba 3.0.14a server in production on a fedora core 3 (kernel 2.6.9-1.667smp) with a least 250 clients (XP Pro SP2) (up to 400 sometimes). A few days ago, a problem appeared with a soft that we are using for a long time. (Petit Robert, a french dictionnary). When someone launch the dictionnary, many clients are freezed when they try to access to the "start

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response