|
Important update for SOTDS Suite!
Basically its left-over bugs when I switched over from non-unicode Purebasic language/compiler to Unicode based only Purebasic language/compiler (SOTDS is programmed in PureBasic).
Some severe bugs that wasn't discovered in previous 3-4 versions or so has now been successfully investigated and fixed!
Technically it renders v2.96, v2.95 and possibly v2.9 completely buggy and unstable. Download this version to ensure proper indexing, constructing and searching behaviours.
::: REVISION HISTORY SOTDS CONSTRUCTOR :::
-----------------------------------------------------------
v1.96 - 23 Aug 2017:
- 01: Replaced a couple of wrong peek and poke, (PokeB, PeekB, PokeC, PeekC and replaced with PeekA and PokeA), since SOTDS is non-unicode.
- 02: Replaced CHR(value) during Writestring() with WriteAsciiCharacter() instead as this caused bugs in all previous versions since v1.9.
- 03: Asc() replaced with *ascii=Ascii() to prevent Unicode vs old-school ASCII bullshit problems.
- 04: Support for chars 129,141,143,144,157 were removed as these are basically blank chars and has no meaning to display/search for.
- 05: Added CPUName() to .INI file (comments).
::: REVISION HISTORY SOTDS SEARCHER :::
-----------------------------------------------------------
v2.96 - 24 Aug 2017:
- 01: Replaced some Asc() with *ascii=AScii() as certain Unicode chars matches 0-255 standard ascii to prevent issues with searching for chars in range 128-160.
- 02: Also made sure All characters from 0-255 (including those which clash with UNICODE stupidiy range 128-160 are illustrated as proper characters within the original 0-255 ASCII range)!
- 03: Replace some CHR(>127) with ascii proper representation instead of that UNICODE bullshit.
- 04: Replaced ReadArrayFromFileByte() with ReadArrayFromFileAsciiCharacter() to allow workaround for bytes over 127 becoming unicode = some wildcard searches failed!
Please review these related article links:
|
Stone Oakvalley's Text Database Searcher (SOTDS) Dashboard