@Flashing Blade...that's what I suspected, but I wanted to be sure. In 16-bit windows, it was somewhat easier, although for the life of me I don't remember exactly how we did it. Probably the very best way to do it the way you want is with a specialized array. The STL has a class that GDK programmers should use : valarray. It might be the ticket for your situation. In the meantime, I can provide you with a utility to make your text file into a flat byte array, but I have a couple of questions. Is it comma-delimited bytes, or what? If it is, you can make a byte array, and use the address to access it any way that you want, but...iirc, a mesh has a header, and consists of floats and maybe also dwords, and depends on many things for its actual format. If you have simply saved the memblock as an encrypted series of bytes...I have a tool that will let you insert it into your data, and you can compile that once, which will take some time, but it will produce an object file that will simply be linked in thereafter. Do you want that?
@bjadams - My bad, you had asked me about that, and I've dropped the ball. Here is a more useful apology, from one of my projects. It goes into the .rc file and you can simply replace your info for mine (only the second strings in the VALUE portion need changes.):
VS_VERSION_INFO VERSIONINFO
FILEVERSION 1,0,0,1
PRODUCTVERSION 1,0,0,1
FILEFLAGSMASK 0x17L
#ifdef _DEBUG
FILEFLAGS 0x1L
#else
FILEFLAGS 0x0L
#endif
FILEOS 0x4L
FILETYPE 0x2L
FILESUBTYPE 0x0L
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904b0"
BEGIN
VALUE "CompanyName", "jinzai studio"
VALUE "FileVersion", "1, 0, 0, 1"
VALUE "InternalName", "qIIIbsp"
VALUE "LegalCopyright", "Copyright (C) 2008"
VALUE "OriginalFilename", "qIIIbsp.dll"
VALUE "ProductName", " qIIIbsp Dynamic Link Library"
VALUE "ProductVersion", "1, 0, 0, 1"
END
END
BLOCK "VarFileInfo"
BEGIN
VALUE "Translation", 0x409, 1200
END
END