Re: Wine error message
On Sat, 4 Aug 2018 07:55:05 -0400 Carl Fink wrote: > For years, my policy has been to use stable on servers and testing > on workstations. For servers i'ts pretty much clear, but in regard to testing vs unstable this was decisive part for me: "Testing has more up-to-date software than Stable, and it breaks less often than Unstable. But when it breaks, it might take a long time for things to get rectified. Sometimes this could be days and it could be months at times. It also does not have permanent security support." (https://www.debian.org/doc/manuals/debian-faq/ch-choosing.html) Sincerely, Gour -- Abandoning all attachment to the results of his activities, ever satisfied and independent, he performs no fruitive action, although engaged in all kinds of undertakings.
Re: Wine error message
On 08/04/2018 07:51 AM, Gour wrote: However, 'stable' is too old for me, although I'll probably put it on my relative's machined and between 'testing' and 'unstable' I believe that the latter is bette option. For years, my policy has been to use stable on servers and testing on workstations. -- Carl Fink c...@finknetwork.com Thinking and logic and stuff at Reasonably Literate http://reasonablyliterate.com
Re: Wine error message
On Sat, 4 Aug 2018 07:16:47 -0400 Carl Fink wrote: > If you're looking for a more stable system, maybe the "unstable" > distribution of Debian is not an ideal choice? Well, in the past I spent >10yrs with rolling distros (Gentoo & Arch) and thought that Fedora might be good option providign newer packages and I had good experience with smoooth upgrades between releases, bつt last incidents were too much and I never experienced such thing with Debian. However, 'stable' is too old for me, although I'll probably put it on my relative's machined and between 'testing' and 'unstable' I believe that the latter is bette option. Sincerely, Gour -- One who is not disturbed in mind even amidst the threefold miseries or elated when there is happiness, and who is free from attachment, fear and anger, is called a sage of steady mind.
Re: Wine error message
On 08/04/2018 06:58 AM, Gour wrote: Few days ago I migrated from Fedora (fc28) where I had serious issues with 4.17.x kernel series experiencing system hangs several times per day when leaving my machine unattended to Debian Sid where there are nothing similar (so far). If you're looking for a more stable system, maybe the "unstable" distribution of Debian is not an ideal choice? -- Carl Fink c...@finknetwork.com Thinking and logic and stuff at Reasonably Literate http://reasonablyliterate.com
Re: Wine error message
On Mon, 23 Jul 2018 14:56:56 +0200 floris wrote: > The Wine version in Debian Stable is very old and unsupported. You > should use the WineHQ packages or use the version from Backports Thank you for helpful advice! Few days ago I migrated from Fedora (fc28) where I had serious issues with 4.17.x kernel series experiencing system hangs several times per day when leaving my machine unattended to Debian Sid where there are nothing similar (so far). However, I have a need to run several apps under Wine, but attempt to install it on my x86_64 was an impossible mission - it seems that wine32 is broken. Finally, after enabling WineHQ repo and installing from there, eveything is fine. :-) Sincerely, Gour -- There is no possibility of one's becoming a yogī, O Arjuna, if one eats too much or eats too little, sleeps too much or does not sleep enough.
Re: Wine error message
Richard Owlett schreef op 2018-07-24 23:00: On 07/23/2018 07:56 AM, floris wrote: Richard Owlett schreef op 2018-07-21 17:02: Just installed/used wine for first time ever. The Wine version in Debian Stable is very old and unsupported. You should use the WineHQ packages or use the version from Backports Did that done dat I've T shirt Which wine version do you use? I attempted to run an installer which asks a typical set of questions to which I chose the defaults. It is setup to run a demo on completion. The demo appears to run correctly. I ran the same installer on a WinXP machine which appears to run identically. I have two problems. On exiting the installer nothing has actually been written to disk Wine uses a hidden folder ~/.wine as it default location. Did you check that location? Non-informative Maybe I don't understand your "nothing has actually been written to disk" But when I try the installer with the default settings, the program is installed in: $WINEPREFIX/drive_c/users//Local Settings/Application Data/OLB (C:\users\\Local Settings\Application Data\OLB) OLBLite.801 PocketOnlineBible.801 and $WINEPREFIX/drive_c/Program Files (x86)/Bible (C:\Program Files (x86)\Bible) Desktop.Idt HelpEng.Chm messages.eng Paragrap.map TutorEng.Chm Dsp.wav IconsOlbDel.ExeSDPath.TxtVIReadMe.Eng Go.Bat Install.Msg Olb.Exe Std.wav WhatsNew.Eng Second, early in the question asking phase, a message appears on my console: $ err:trash:TRASH_MoveFileToBucket Couldn't move file That is the message that prompted this post. What is it trying to say? Is there a catalog of Wine error messages (didn't find one)? In Wine version 3.12 there isn't such message. Oh *NO* u answered question ??? Every two weeks there is a new wine version with a lot of bug fixes. Probably this bug is resolved. Now only a "fixme" warning is printed: 0009:fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented To answer your "is there a catalog of Wine error messages?" question. No, there isn't a list with "error x happend -> the message means this -> you should do this" You could read the FAQ, the manual and the forum on winehq.org if you look for error messages. *SNICKER* I was vainly attempting to determine that what I saw on my console was a WINE or an APPLICATION error message. It has been *YEARS* since I've actually used my WinXP machine. Don't know how to copy/find appropriate file(s) on my WinXp machine in order that WINE might attempt to execute. --- Floris
Re: Wine error message
On 07/25/2018 04:04 AM, Curt wrote:
On 2018-07-24, Richard Owlett wrote:
I was vainly attempting to determine that what I saw on my console was a
WINE or an APPLICATION error message.
Looks like it's coming from wine.
https://github.com/wine-mirror/wine/blob/master/dlls/shell32/trash.c
static BOOL TRASH_MoveFileToBucket(TRASH_BUCKET *pBucket, const char *unix_path)
{
struct stat file_stat;
char *trash_file_name = NULL;
char *trash_path = NULL;
BOOL ret = TRUE;
if (lstat(unix_path, _stat)==-1)
return FALSE;
if (!file_good_for_bucket(pBucket, _stat))
return FALSE;
trash_file_name = create_trashinfo(pBucket->info_dir, unix_path);
if (trash_file_name == NULL)
return FALSE;
trash_path = SHAlloc(strlen(pBucket->files_dir)+strlen(trash_file_name)+1);
if (trash_path == NULL) goto error;
lstrcpyA(trash_path, pBucket->files_dir);
lstrcatA(trash_path, trash_file_name);
if (rename(unix_path, trash_path)==0)
{
TRACE("rename succeeded\n");
goto cleanup;
}
/* TODO: try to manually move the file */
ERR("Couldn't move file\n");
**
Thank you.
Re: Wine error message
On 2018-07-24, Richard Owlett wrote:
>
> I was vainly attempting to determine that what I saw on my console was a
> WINE or an APPLICATION error message.
>
Looks like it's coming from wine.
https://github.com/wine-mirror/wine/blob/master/dlls/shell32/trash.c
static BOOL TRASH_MoveFileToBucket(TRASH_BUCKET *pBucket, const char *unix_path)
{
struct stat file_stat;
char *trash_file_name = NULL;
char *trash_path = NULL;
BOOL ret = TRUE;
if (lstat(unix_path, _stat)==-1)
return FALSE;
if (!file_good_for_bucket(pBucket, _stat))
return FALSE;
trash_file_name = create_trashinfo(pBucket->info_dir, unix_path);
if (trash_file_name == NULL)
return FALSE;
trash_path = SHAlloc(strlen(pBucket->files_dir)+strlen(trash_file_name)+1);
if (trash_path == NULL) goto error;
lstrcpyA(trash_path, pBucket->files_dir);
lstrcatA(trash_path, trash_file_name);
if (rename(unix_path, trash_path)==0)
{
TRACE("rename succeeded\n");
goto cleanup;
}
/* TODO: try to manually move the file */
ERR("Couldn't move file\n");
**
--
Boris sober and Boris drunk are such different people, they’ve never even met.
-- Sergei Dovlatov, Pushkin Hills
Re: Wine error message
On 07/23/2018 07:56 AM, floris wrote: Richard Owlett schreef op 2018-07-21 17:02: Just installed/used wine for first time ever. The Wine version in Debian Stable is very old and unsupported. You should use the WineHQ packages or use the version from Backports Did that done dat I've T shirt I attempted to run an installer which asks a typical set of questions to which I chose the defaults. It is setup to run a demo on completion. The demo appears to run correctly. I ran the same installer on a WinXP machine which appears to run identically. I have two problems. On exiting the installer nothing has actually been written to disk Wine uses a hidden folder ~/.wine as it default location. Did you check that location? Non-informative Second, early in the question asking phase, a message appears on my console: $ err:trash:TRASH_MoveFileToBucket Couldn't move file That is the message that prompted this post. What is it trying to say? Is there a catalog of Wine error messages (didn't find one)? In Wine version 3.12 there isn't such message. Oh *NO* u answered question ??? You could read the FAQ, the manual and the forum on winehq.org if you look for error messages. *SNICKER* I was vainly attempting to determine that what I saw on my console was a WINE or an APPLICATION error message. It has been *YEARS* since I've actually used my WinXP machine. Don't know how to copy/find appropriate file(s) on my WinXp machine in order that WINE might attempt to execute.
Re: Wine error message
Richard Owlett schreef op 2018-07-21 17:02: Just installed/used wine for first time ever. The Wine version in Debian Stable is very old and unsupported. You should use the WineHQ packages or use the version from Backports I attempted to run an installer which asks a typical set of questions to which I chose the defaults. It is setup to run a demo on completion. The demo appears to run correctly. I ran the same installer on a WinXP machine which appears to run identically. I have two problems. On exiting the installer nothing has actually been written to disk Wine uses a hidden folder ~/.wine as it default location. Did you check that location? Second, early in the question asking phase, a message appears on my console: $ err:trash:TRASH_MoveFileToBucket Couldn't move file That is the message that prompted this post. What is it trying to say? Is there a catalog of Wine error messages (didn't find one)? In Wine version 3.12 there isn't such message. You could read the FAQ, the manual and the forum on winehq.org if you look for error messages. --- Floris
Wine error message
Just installed/used wine for first time ever. I attempted to run an installer which asks a typical set of questions to which I chose the defaults. It is setup to run a demo on completion. The demo appears to run correctly. I ran the same installer on a WinXP machine which appears to run identically. I have two problems. On exiting the installer nothing has actually been written to disk Second, early in the question asking phase, a message appears on my console: $ err:trash:TRASH_MoveFileToBucket Couldn't move file That is the message that prompted this post. What is it trying to say? Is there a catalog of Wine error messages (didn't find one)? I have reason to doubt the first problem is a bug in wine &/or Debian. Long after the error message above appears, there is an *installer* warning that "a non wine program is being executed under wine". I suspect that the wine compliant version requires a paid unlock code - there are ambiguities on the website that I've already reported. I suspect the error message quoted above is either a wine bug or something strange about my system. The installer is [install_advance_5.40.00.00.exe] from [https://onlinebible.net/]. Comments? TIA
