zabkat support forum

So, I just upgraded to version 4.0.0.0 after using 1.8.1.4 for ages - newer versions don't really add anything I need, but I use x2 daily and want to support the great application, so there's that. The new version has added a filter/select/search thing as part of the address bar - that seems like a ...

Thanks for clearing that up, Nikos - I might look into getting a more recent version

It would be nice if you didn't try to be sneaky in the license manager - it's not stopping the pirates (cracks appear shortly enough after new version releases), but it does cause some annoyances for legitimate customers (at least that's the case for 1.8.x series). It's annoying having to launch wit...

if you're dealing with paths and filenames, do yourself a favor: stop working on character buffers, move up an abstraction level and find/design yourself a Path class. It centralizes where you have to deal with these issues, reduces the risk of bugs, and makes your code clearer you are perfectly ri...

Kilmatead, there is a pretty large number of functions in libc that are only safe to use in special situations, which cannot be used safely in the general way (which people often do use them) - so the warnings in MSDN are entirely appropriate. A number of these functions didn't have safe alternative...

too much of tl;dr; and little actual experimentation before stating opinions in the strongest terms, you must be the reincarnation of Aristotle ;) Ah, an ad hominem instead of dealing with the contents? ;-) I've done a fair amount of experimentation myself, and the docs haven't always been right - ...

This hints a deeper (no pun intended) problem in windows kernel, No, it hints at the Win32 subsystem having lots of MAX_PATH dependencies, not the kernel. On windows 10 you can have super deep paths even on USB sticks (FAT32 !?) which is surprising Did you verify the FS was FAT32? There's nothing s...

you have completely missed the point of the article. As you can see from the results when the "no buffering" flag is used, again after 32KB buffers the speed doesn't improve, which again is the same as in the cached reads. Nikos, did you get to perform some tests with fast drives, like mo...

"Seems to work" doesn't go very well with security. Depends if you otherwise know the sources. No, it doesn't - security needs to be bloody well tested, especially for critical infrastructure code. Yes, the OpenBDS developers are pretty damn good, and I have a lot of confidence in them - ...

As for running LibReSSL... it's a very good initiative, but I certainly don't hope you're running it in production yet - especially not if you're running it on anything but OpenBSD. I run it on FreeBSD where it seems to work (except for some occasional patches in various ports) rather well. No worr...

I doubt there's a thing like "secure keygens". After your blog post had been released, OpenSSL was proven to be an insecure pile of wrappers for not working algorithms. Welcome to open source. Tuxman, OpenSSL is a stinking pile of crap, but it seems you don't really understand how it's a ...

You're welcome

nothing is impossible and I don't really know about this, but I would find it astonishing if MS guys are not aware of it and they don't provide at least some registry tweak to control such self-destructing behavior !? If you don't ask for non-buffered I/O, why shouldn't the cache manager cache? :) ...

That's a very simplistic benchmark, and it doesn't really fit any real-world data access patterns :) - Since you're repeatedly reading an extremely small file, with buffering on, you're essentially measuring the cost of security checks and usermode<>kernelmode switching. If you want any kind of sens...

All these filesystem objects originate from UNIX Are you sure they didn't originate from VMS? ;-) Joke aside, it's interesting it took so long before we got symlinks on NT. Junctions are nice, but I've always had the impression they were really lowlevel kernel feature that somebody figured wouldn't...