http://bugs.winehq.org/show_bug.cgi?id=4055
john(a)t-tec.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1525 is|0 |1
obsolete| |
------- Additional Comments From john(a)t-tec.com.au 2006-06-02 19:33 -------
Created an attachment (id=1838)
--> (http://bugs.winehq.org/attachment.cgi?id=1838&action=view)
output: I connected to ICD2 and then tried to erase, using MPLAB 7.2, wine
0.9.7
There has been a slight improvement since I last tried this. Now, with Wine
0.9.7 and MPLAB 7.2, I can connect to the ICD2 and it correctly identifies the
device.
However, when I go to the next part of what I want to do, erasing the chip, it
gives the same errors that I used to experience when trying to connect.
Here's a new file of the output from "WINEDEBUG=+comm wine MPLAB". I don't know
if there is any real difference with the older one.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4501
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4498
tony.lambregts(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |NoAppDBEntry
------- Additional Comments From tony.lambregts(a)gmail.com 2006-06-02 19:24 -------
Could you please submit an enry in the AppDB for this application
http://appdb.winehq.org
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4502
------- Additional Comments From a_villacis(a)palosanto.com 2006-06-02 18:11 -------
Created an attachment (id=1837)
--> (http://bugs.winehq.org/attachment.cgi?id=1837&action=view)
Test case which demostrates the bug
This is a sample VB project with compiled EXE, which triggers the bug. The app
displays a form with a DTPicker and two buttons. Clicking on any one of the
buttons is supposed to assign a date to the DTPicker (as shown in the source
code), but instead a 'Type mismatch' error is displayed, and the application
terminates. At the same time, the error message appears in the console.
Program requires MSVBVM60.DLL, not included because it makes sample too large
to post.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4502
Summary: Regression: DatePicker from MSCOMCT2.OCX causes Type
Mismatch on assignment to Value
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: wine-ole
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: a_villacis(a)palosanto.com
Wine 0.9 works correctly with VB programs that use the DTPicker control from
MSCOMCT2.OCX.
Current CVS fails at the moment the VB program tries to assign the Value
property from a Date variable:
err:ole:ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT from VT_DATE
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3166
------- Additional Comments From robert(a)paulsen.homeip.net 2006-06-02 17:39 -------
Still no joy.
> rm -rf .wine/
> wine --version
wine: creating configuration directory '/home/robert/.wine'...
ln: creating symbolic link `/home/robert/.wine-J9HCmP/dosdevices/m:/usbdisk_4'
to `/media/usbdisk_4': Permission denied
wine: wineprefixcreate failed while creating '/home/robert/.wine'.
If it is creating .wine, how come it tries to use .wine-J9HCmP ?
I can create the directory structure and soft link manually with no problem.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=4500
------- Additional Comments From truiken(a)gmail.com 2006-06-02 17:21 -------
Can you add this test to the msvcrt test suite and submit the patch to
wine-patches(a)winehq.org?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4497
------- Additional Comments From b.buschinski(a)web.de 2006-06-02 16:18 -------
can confirm
same here
OS: Gentoo AMD64
Kernel: 2.6.15.1 (SMP)
GFX Card: NVidia 6600 GT (drivers: 8178)
RAM: 1024 MB
Wine Ver: CVS 20060206
without -heapsize 512000
it crashs too, but no "Out of Memory" window apears
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4501
Summary: Change to dlls/wineps/pen.c breaks printing in qcharts
Product: Wine
Version: 0.9.7.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-gdi-(printing)
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cdunn42(a)yahoo.com
CC: dmitry(a)codeweavers.com
Running QCharts (http://www.qcharts.com) stock charting software, after wine
0.9.7, studies (moving averages, indicators, etc) on a printed chart no longer
keep the same line thickness they have on screen.
This is subscription software, so may be difficult to test, but as I am a
subscriber, I'll help if I can.
After looking at the ChangeLog and the source code in dlls/wineps/pen.c, I found
that if I backed out the change of 2/1/06 by replacing :
physDev->pen.width = logpen.lopnWidth.x;
if (logpen.lopnStyle & PS_GEOMETRIC)
{
physDev->pen.width = PSDRV_XWStoDS( physDev, physDev->pen.width );
if(physDev->pen.width < 0) physDev->pen.width = -physDev->pen.width;
}
with the previous code :
physDev->pen.width = PSDRV_XWStoDS(physDev, logpen.lopnWidth.x);
if(physDev->pen.width < 0)
physDev->pen.width = -physDev->pen.width;
then the problem went away, charts print with the correct line thicknesses.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4500
Summary: msvcrt: regression in very simple test app.
Product: Wine
Version: CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Keywords: regression, download
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
Hi, there have been several regressions in msvcrt in the SeriousSam demo. I'll
leave bug 4482 for a regression that took place between wine's june and july
version 2005. I think there's also a bug/regression in _vsnprintf
here's modified sample from msdn; modifications are based on what SeriousSam
passes to _vsnprintf:
#include <stdarg.h>
#include <wtypes.h>
void VarArg(LPCSTR formatstring, ...)
{
int nSize = 0;
char buff[255];
va_list args;
va_start(args, formatstring);
nSize = _vsnprintf( buff, sizeof(buff), formatstring, args);
printf("nsize=%d\n", nSize);
}
void main() {
VarArg("Players\Player%d.plr", "Players\Player0.plr");
VarArg("Cannot open file `%s' (%s) ()", "");
}
The exe can be found at http://bugs.winehq.org/attachment.cgi?id=1829&action=view
it gives:
WINEDLLOVERRIDES="msvcrt=n" wine a.exe
nsize=24
nsize=25
same result with wine 0.9.5
with wine 0.9.7:
wine a.exe
nsize=24
nsize=33
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.