Quote:
-kwag |
What? Can you smell it from over there in PR? :mrgreen:
|
Quote:
-kwag |
Kudos!
@Kwag
I've tested Kutter out with a VOB of 1 GB from Harry Potter I, where I'd wanna split files about 100 MB. The app done the job with precision and quickness. Kudos, |
Thanks danpos :)
All feedbacks are always welcome :cool: -kwag |
@ Karl
The LongLong issue can be solved uing a simple strucure! Structure int64 LongHi.l LongLow.l EndStructure Amount.int64 APIFunction(@Amount) This makes you able to use for example an API function which does apply the result of a big filesize for instance to the variable "Amount". BUT that int64 imho is unsigned, so watch out. In case if a DirectShow usage for instance in PB this is the trick: Code:
Structure int64 http://pbosl.purearea.net/pbosl_win.zip Including: Code:
UInt64_ulong2uint64 load 32-bit unsigned long into 64-bit unsigned integer 64 http://www.purearea.net/pb/CodeArchi...Longs_64Bit.pb |
Hi Andrej,
Thanks for the code. This is all fine for memory structures, but there's no (simple) way to read from a file past the 2GB limit, unless I use Win32 API in another way. The problem is when you try to read past a file pointer boundary of 2GB. All I/O calls ( ReadFile, LOF, ReadData, etc. ) work on Long, and will never return data past the limit. So the only solution is to use Win32 API calls, and then rewrite all file seeking/accesing routines, because the built in functions on PB won't work. I'm considering rewriting the utility in C, just for the hell of it :lol: Then when PB gets updated, I'll recompile it again in PB :cool: I'll probably recode Kutter! in C in a matter of hours ;) -kwag |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.