Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing export on WIN98SE, etc. (3.x) #16

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 13 comments
Closed

Missing export on WIN98SE, etc. (3.x) #16

GoogleCodeExporter opened this issue Mar 24, 2015 · 13 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Trying to run it on Win98 (and also probably WinMe)
2.
3.

What is the expected output? 
For it to run.

What do you see instead?
If you try to run xdelta30m.x86-32.exe on Win98, you'll get this error message:

The XDELTA30M.X86-32.EXE file is linked to missing export
KERNEL32.DLL:GetFileSizeEx.

What version of the product are you using? 
xdelta30m.x86-32.exe

On what operating system?
Win98SE

Please provide any additional information below.
I'm sure you already know this...but what the heck?

According to this forum, to correct the problem, you change GetFileSizeEx
to GetFileSize, and it should now work on Win98/Me:
http://forum.doom9.org/showpost.php?p=455861&postcount=30

Original issue reported on code.google.com by segnin...@gmail.com on 31 Jan 2007 at 5:40

@GoogleCodeExporter
Copy link
Author

GetFileSizeEx is needed for 64bit files. I may have to make two releases to 
solve
this. I'll investigate.

Original comment by josh.mac...@gmail.com on 1 Feb 2007 at 6:02

  • Changed title: Missing export on WIN98SE, etc.
  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by josh.mac...@gmail.com on 2 Feb 2007 at 7:53

  • Changed title: Missing export on WIN98SE, etc. (3.x)

@GoogleCodeExporter
Copy link
Author

I think the 64-bit-filesize problem is definitely not relevant when working 
with 
files on the local file system on Win9x since the FAT32 file system only 
supports 
files up to 4 GB in size.
I wonder whether Win9x supports larger file sizes when working with network 
files...

Under WinXP I could get GetFileSize() to return the correct 64-bit filesize of 
a 6 
GB file by using the following code:
__int64 size;
DWORD sizeHigh, sizeLow;
sizeLow = ::GetFileSize( hFile, &sizeHigh );
size = ( __int64( sizeHigh ) << 32 ) | __int64(sizeLow);


Original comment by as...@gmx.net on 25 Mar 2007 at 3:19

@GoogleCodeExporter
Copy link
Author

Let me know if this installer solves the problem for you:

http://code.google.com/p/xdelta/downloads/detail?name=xdelta30q.msi

Original comment by josh.mac...@gmail.com on 25 Mar 2007 at 7:14

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by josh.mac...@gmail.com on 25 Mar 2007 at 7:14

  • Added labels: Milestone-Release3.0

@GoogleCodeExporter
Copy link
Author

Statically linked:
http://code.google.com/p/xdelta/downloads/detail?name=xdelta3q.1.msi

Original comment by josh.mac...@gmail.com on 25 Mar 2007 at 11:28

@GoogleCodeExporter
Copy link
Author

Still missing the following DLL-Imports under Win98: GetFileSizeEx, 
SetFilePointerEx.
GetFileSizeEx could be replaced by GetFileSize and SetFilePointerEx by 
SetFilePointer - but only GetFileSize supports 64-bit file sizes (for network 
files). So I think there is no way to process 64-bit files under Win9x.
I wonder whether there really is a need for xdelta to support large files under 
these old systems.

Original comment by as...@gmx.net on 26 Mar 2007 at 2:38

@GoogleCodeExporter
Copy link
Author

OK -- leaving this issue open.  I want to avoid using different function 
signatures
in different builds, we'll see if that's possible.

Original comment by josh.mac...@gmail.com on 28 Mar 2007 at 4:22

@GoogleCodeExporter
Copy link
Author

Maybe my last comment was a bit unclear. Both GetFileSize() and 
SetFilePointer() are 
documented to work with 64-bit file sizes and are available for all Win32 OS.
The only exception is that the Win9x family (Windows Me/98/95) does not support 
64-
bit offsets for SetFilePointer(). 

Original comment by as...@gmx.net on 29 Mar 2007 at 7:50

@GoogleCodeExporter
Copy link
Author

I see, so we can't do a 64bit seek on Windows98.

In fact the encoder does not seek so it can be fixed, but the decoder may be 
forced
to seek if it is configured w/ less memory than the encoder was.

I would like to fix this so that < 2GB (4GB?) files work on Windows98, at least.

Original comment by josh.mac...@gmail.com on 30 Mar 2007 at 3:33

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by josh.mac...@gmail.com on 14 Dec 2007 at 9:38

  • Removed labels: Milestone-Release3.0

@GoogleCodeExporter
Copy link
Author

Fixed in SVN 221.  I've had an accident w/ my windows laptop and won't be able 
to
make a new release very soon.  But, it should build from source.

Original comment by josh.mac...@gmail.com on 15 Dec 2007 at 12:43

@GoogleCodeExporter
Copy link
Author

Fixed.  See issue 56.

Original comment by josh.mac...@gmail.com on 15 Dec 2007 at 1:56

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant