-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
BTW: I use wine 20010112 since the last snapshot 20010418 does not work on my machine (unhandled exception).
Here is the last line from the logfile when starting wine with '+reg': trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6d10)
- -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
[HKEY_LOCAL_MACHINE\Software\Classes\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}"
But don't think that your Wine config is broken if you don't have registry settings from an already installed Office ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 13:05, Andreas Mohr wrote:
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
[HKEY_LOCAL_MACHINE\Software\Classes\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}"
But don't think that your Wine config is broken if you don't have registry settings from an already installed Office ?
Hmm ... I did not install Office on my machine, just copied the following files from my Windows NT machine into a separate directory:
- - winword.exe - - mso97.dll - - wwintl32.dll
To be honest: I even have not installed Windows at all on this machine although I have a license for it.
The files stated above are enough to resolve the linker dependencies.
Additionally I added a font alias:
"Alias0" = "Tahoma,-adobe-helvetica-"
This is because I did not get xfstt work together with my Windows Exceed X Server (to use the original tahoma.ttf files). This suppresses the error message saying that it could not find Tahoma font.
- -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 14:09, Heiko Nardmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 13:05, Andreas Mohr wrote:
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
[HKEY_LOCAL_MACHINE\Software\Classes\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}"
And now I have to say that this did not work. Sorry ...
Any other idea?
Here are the lines of debug with +all which contain references to this SharedMemory stuff; maybe someone can tell me what to do:
Call advapi32.211: RegDeleteKeyA(80000000,3079075c "Office.SharedMemory.1") ret=307907f6 fs=008f Call ntdll.419: RtlInitAnsiString(405b6b88,3079075c "Office.SharedMemory.1") ret=407c591a fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000016 ret=407c591a fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(405b6b90,405b6b88,00000001) ret=407c5926 fs=008f trace:heap:HeapAlloc (40360000,00000002,0000002c): returning 403a7a2c Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c5926 fs=008f Call ntdll.132: NtOpenKey(405b6bd4,00000000,405b6b98) ret=407c593d fs=008f trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6bd4) 080687e8: open_key( parent=-2147483648, access=00000000, name=L"Office.SharedMemory.1" ) Create key \Machine\Software\Classes Open key ERROR 080687e8: open_key() = c0000034 { hkey=0 } Ret ntdll.132: NtOpenKey() retval=c0000034 ret=407c593d fs=008f Call ntdll.396: RtlFreeUnicodeString(405b6b90) ret=407c5945 fs=008f trace:heap:HeapFree (40360000,00000002,403a7a2c): returning TRUE Ret ntdll.396: RtlFreeUnicodeString() retval=00000001 ret=407c5945 fs=008f Call ntdll.466: RtlNtStatusToDosError(c0000034) ret=407c594b fs=008f Ret ntdll.466: RtlNtStatusToDosError() retval=00000002 ret=407c594b fs=008f Ret advapi32.211: RegDeleteKeyA() retval=00000002 ret=307907f6 fs=008f Call advapi32.211: RegDeleteKeyA(80000000,3079075c "Office.SharedMemory.1") ret=307907f6 fs=008f Call ntdll.419: RtlInitAnsiString(405b6b88,3079075c "Office.SharedMemory.1") ret=407c591a fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000016 ret=407c591a fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(405b6b90,405b6b88,00000001) ret=407c5926 fs=008f trace:heap:HeapAlloc (40360000,00000002,0000002c): returning 403a7a2c Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c5926 fs=008f Call ntdll.132: NtOpenKey(405b6bd4,00000000,405b6b98) ret=407c593d fs=008f trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6bd4) 080687e8: open_key( parent=-2147483648, access=00000000, name=L"Office.SharedMemory.1" ) Open key ERROR 080687e8: open_key() = c0000034 { hkey=0 } Ret ntdll.132: NtOpenKey() retval=c0000034 ret=407c593d fs=008f
- -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 14:40, Heiko Nardmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 14:09, Heiko Nardmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 13:05, Andreas Mohr wrote:
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
This happens with CVS version, too, which I just compiled and installed.
- -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50
Heiko Nardmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 13:05, Andreas Mohr wrote:
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
[HKEY_LOCAL_MACHINE\Software\Classes\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}"
But don't think that your Wine config is broken if you don't have registry settings from an already installed Office ?
Hmm ... I did not install Office on my machine, just copied the following files from my Windows NT machine into a separate directory:
- winword.exe
- mso97.dll
- wwintl32.dll
To be honest: I even have not installed Windows at all on this machine although I have a license for it.
The files stated above are enough to resolve the linker dependencies.
You will need to run the installation program or manually copy all the registry entries from an existing installation. The Microsoft Office applications put tons of stuff in the registry which is necessary for them to run.
-- James Juran jamesjuran@alumni.psu.edu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 23:46, James Juran wrote:
Heiko Nardmann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 21 May 2001 13:05, Andreas Mohr wrote:
On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote:
When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then.
So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain?
[HKEY_LOCAL_MACHINE\Software\Classes\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}"
But don't think that your Wine config is broken if you don't have registry settings from an already installed Office ?
Hmm ... I did not install Office on my machine, just copied the following files from my Windows NT machine into a separate directory:
- winword.exe
- mso97.dll
- wwintl32.dll
To be honest: I even have not installed Windows at all on this machine although I have a license for it.
The files stated above are enough to resolve the linker dependencies.
You will need to run the installation program or manually copy all the registry entries from an existing installation. The Microsoft Office applications put tons of stuff in the registry which is necessary for them to run.
I would have expected to be able to go step for step through all problems which I can see in the wine log messages and then solve them. Interestingly enough I just see that I don't have a registry entry called "Office.SharedMemory.1" on my Windows NT 4.0 machine (used regedit and searched registry for "SharedMemory" string). How can this be???
-- James Juran jamesjuran@alumni.psu.edu
- -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50
-
Andreas Mohr -
Heiko Nardmann -
James Juran