Bug #20115 | Start problem | ||
---|---|---|---|
Submitted: | 28 May 2006 18:56 | Modified: | 31 May 2006 19:56 |
Reporter: | Dr. ViRuS WhiteHat | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench Preview | Severity: | S1 (Critical) |
Version: | 1.0.6 | OS: | Windows (Windows XP SP2) |
Assigned to: | CPU Architecture: | Any |
[28 May 2006 18:56]
Dr. ViRuS WhiteHat
[29 May 2006 12:41]
Donald Martin
Verified - Same exact problem, same O.S. Version 1.0.6
[31 May 2006 19:56]
Jorge del Conde
Hi! I can't reproduce this bug under both, WinXP/SP2 and WinXP64. Can you try to reinstall MySQL Workbench and see if that helps or not ? Thanks a lot.
[7 Jun 2006 23:58]
Yudhi Widyatama
Same thing happened here, using Windows 2000 SP4. Remembering that 0xc000001d means ILLEGAL_INSTRUCTION, an additional fact is that my system is running on an antique Pentium II-333MHz. Perhaps one of the dependencies uses Pentium III instructions ?
[19 Jun 2006 6:03]
Martin Schneider
I've got exactly the same Problem on my machine. Running Windows XP Pro SP2 on an Athlon 1300 MHz, freshly installed windows, mysql-5.0.22-win32.zip and mysql-workbench-1.0.6-beta-win32.msi