If this issue still can be reproduced with Unshield 1.4.3, then please
provide the data*.cab data*.hdr files for download somewhere and post the
link in a bug report at https://github.com/twogood/unshield/issues
Best regards,
David Eriksson
Quite late response, but orange is the wrong tool for this job.
Use unshield to extract the InstallShield CAB files for Civ4.
Best regards,
David Eriksson
The new home for unshield is at github: https://github.com/twogood/unshield
Releases are available at https://github.com/twogood/unshield/releases
Thanks,
David
Package: unshield
Version: 0.6-3
Severity: wishlist
Dear Maintainer,
I have just released version 1.0 of unshield, including patches for #721933
and #260174
Best regards,
David Eriksson
-- System Information:
Debian Release: wheezy/sid
APT prefers raring-updates
APT policy: (500
Package: root-plugin-hbook
Version: 5.18.00-2.2~lenny1
Severity: important
I try to run h2root with any argument, both real hbook/files and dummy
arguments like "a", and I always get this error message:
LOCB/LOCF: address 0x7f8e65787e40
I suggest that the packaging rules are updated to run ./configure with
--sysconfdir=/etc
See also SynCE bug [ 1962630 ] synce-serial.default.new: No such file or
directory
http://sourceforge.net/tracker/index.php?func=detail&aid=1962630&group_id=30550&atid=399601
Cheers,
David
--
To UNSU
Hi,
The error is actually that orange fails to identify the MS Cabinet files
as such when they are in the .rsrc section. I have committed the patch
below upstream. It will cause the following files to be extracted by
orange from mbutton.exe:
installer.StrongARM.cab
rsrc-0064-0004-
On Thu, 2006-09-14 at 08:34 +0200, Wouter Michiel Koolen-Wijkstra wrote:
> Package: librra0-tools
> Version: 0.9.1-1
> Severity: normal
>
>
> The attached VEVENT file causes rra-appointment-from-vevent to segfault. This
> VEVENT file was obtained
> using the synchronization command of the raki
On Thu, 2005-08-11 at 11:19 -0700, Matt Kraai wrote:
> [snip]
>
> The attached patch eliminates the warnings, which allows the build to
> succeed.
This has already been corrected upstream.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sou
This is now fixed upstream.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Andreas,
Thanks for the patch; I've applied it upstream.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
--
To UNSUBSCRIBE, email to [
t; What does:
> hald --verbos=yes --daemon=no
>
> print?
I get about the same error, my mount point gets called "Ap":
http://www.2good.nu/blandat/hald-mountpoint.log
Here is the first occurence of "Ap":
18:28:37.011 [I] linux/block_class_device.c:119: volume.label =
12 matches
Mail list logo