View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002848 | MMW v4 | Burning / Disc Handling | public | 2007-02-20 21:28 | 2007-03-19 18:34 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002848: Update to latest version of hpcde sdk | ||||
| Description | I've posted the latest version of the SDK to ftp server /burning. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1021 | ||||
|
|
I am missing the installation package for msvc60 (Microsift Visual Studio 6.0) which we use for hpcdburn.dll compiling. There are present a packages only for msvc2003 and msvc2005. Is it possible to upload the package for msvc60 too? |
|
|
Checking with primo...for whatever reason they didn't include an msvc60 version. |
|
|
Hi Russell VC60 static libraries are not supported anymore, due to Microsoft discontinuing support for VC60. If you develop using VC60 please use PrimoBurner DLLs that come with the VC2003 or VC2005 packages. Thank you PrimoBurner SDK Support http://www.primoburner.com |
|
|
I've tested it, it is a way, but we have to use 6 more files somewhere in the MediaMonkey installation folder (i.e. DataCDU.dll, hpCDEU.dll, HfsU.dll, AudioCDU.dll,DataCDU.lib, hpCDEU.lib, HfsU.lib, AudioCDU.lib). And this is not ideal and in addition it takes more disc space, because we use only some functions from these whole libs. So there should be considered whether developing of hpCDBurn.dll under MSVC2005 could be a better choice? I will discuss with Jiri once he is back from holiday. |
|
|
Ack. Leaving it on your plate. |
|
|
Assigning to Ludek to update projects and building batches so that hpcdeburn.dll is compiled using MSVC2005. |
|
|
Resolved in revision 2498. |
|
|
Verified 1023: Playback, Rip, Burn Audio CD, Burn Data CD. There was a problem with CD-text, however, I'm not certain that it is related to this change, so I'll enter it as a separate bug. |
