Re: [Ql-Users] QLTools - 2.15.5 available

2019-02-05 Thread Norman Dunbar via Ql-Users
Hi Wolf, On 05/02/2019 14:01, Wolfgang Lenerz via Ql-Users wrote: int nbrOfSectorsInMap=firstSector.getShort(WinDrive.QWA_SCTM)&0x; // that many sectors are supposed to be in the fat int temp=nbrOfSectorsInMap/(firstSector.getShort(WinDrive.QWA_SCTG)&0x); if (nbrOfSectorsInMap %

Re: [Ql-Users] QLTools - 2.15.5 available

2019-02-05 Thread Wolfgang Lenerz via Ql-Users
Hi, this is the comment I wrote to myself for SMSQmulator in this respect: " Patch for badly constructed drives, like those built by qxltools. These drives do NOT have cluster entries for the FAT(). They just indicate the number of sectors taken by the FAT. I presume that it can then be

Re: [Ql-Users] QLTools - 2.15.5 available

2019-02-05 Thread Norman Dunbar via Ql-Users
On 05/02/2019 10:07, pgraf--- via Ql-Users wrote: Hi Peter, Can you give me an example of how to reproduce the problem(s) you are seeing? I've just created a 20 MB qxl.win with no problems. (So far!) Unfortunately not right now, and my memory is vague. I think that all issues were gone with

Re: [Ql-Users] QLTools - 2.15.5 available

2019-02-05 Thread pgraf--- via Ql-Users
Hi Norm, > > Sounds good. I could compile qxltools, but that was long ago. My concern > > are image sizes over 16 MB and some strange characters in the > > commandline output. > > What problems do you have with 16MB files? I presume you mean that the > qxl.win file is over 16Mb, and it's not a

Re: [Ql-Users] QLTools - 2.15.5 available

2019-02-05 Thread Norman Dunbar via Ql-Users
On 04/02/2019 17:25, Peter Graf wrote: Sounds good. I could compile qxltools, but that was long ago. My concern are image sizes over 16 MB and some strange characters in the commandline output. What problems do you have with 16MB files? I presume you mean that the qxl.win file is over 16Mb,