On Wed, Jun 3, 2020, 15:41 David Haslam <dfh...@protonmail.com> wrote:
> The only AV that I use is Windows Security Essentials. > This has never caused me any issues with other Sword utilities, so I doubt > it could be the culprit for xml2gbs. There's nothing in its quarantine > storage. > Can you try running the import with that disabled? It's still a worthwhile avenue to explore. --Greg > > I noticed during a further test earlier this evening that during the > fleeting existence of both files, their sizes never exceeded *0 bytes*. I > suppose therefore that no data is being written to them, and tentatively > surmise that in case of build errors, xml2gbs might have a routine to > remove empty files as it finishes. It's a plausible conjecture. > > Timmy has since built the module under Linux and sent it to me. It works > fine. > He and another list member have both offered to try using xml2gbs under > Windows 10. > *That may await tomorrow.* > > Best regards, > > David > > Sent with ProtonMail <https://protonmail.com> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, 3 June 2020 19:46, Greg Hellings <greg.helli...@gmail.com> > wrote: > > > > On Wed, Jun 3, 2020 at 12:41 PM David Haslam <dfh...@protonmail.com> > wrote: > >> Well I guess there's at least one *Windows 10* user on this mailing >> list, so it would be useful to know whether the *same issue* occurs on >> that supported operating system, even if one accepts that *Windows 7* is >> past its official end of support for *non-enterprise* customers. >> > > No one is doubting the users in Windows. Windows just has never been a > supported venue for the utilities. They are not really designed to be > end-user-supported in the same way that the applications and library are. > And, as such, there aren't really utility developers on Windows. > > >> >> *Aside*: There's still a very large install base of Windows 7 systems >> worldwide. Many businesses have never migrated to Windows 10. >> >> Creating two files (according to design) and then almost immediately >> deleting them is very bizarre. There must be a rational explanation. It >> might turn out to be so simple that (in theory at least) it could be very >> easily rectified. >> > > I have only seen this in one scenario, before, and that was virus/malware > monitoring software. Do you have any such security software installed? Can > you check to see if it is getting in the way? Try seeing if it has > quarantined the files, if so, and then try running with it disabled. > > --Greg > >> >> Best regards, >> >> David >> >> Sent with ProtonMail <https://protonmail.com> Secure Email. >> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> On Wednesday, 3 June 2020 18:10, Greg Hellings <greg.helli...@gmail.com> >> wrote: >> >> >> >> On Wed, Jun 3, 2020 at 9:50 AM David Haslam <dfh...@protonmail.com> >> wrote: >> >>> Be that as it may, it would be helpful if someone could go the extra >>> mile beyond the call of duty. >>> >> >> Don't hold your breath. None of the developers of the utilities are >> Windows users, nor do they support running an unsupported version of the >> tools on an unsupported version of the operating system. >> >> >>> As it is, I have no means to test a new GenBook module until it’s been >>> put in CrossWire Beta by Dom. >>> >> >> https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/ >> >> https://www.virtualbox.org/ >> >> >> https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html >> >> https://docs.microsoft.com/en-us/windows/wsl/install-win10 >> >> That is decidedly not true. >> >> --Greg >> >>> >>> Kind regards, >>> >>> David >>> >>> >>> Sent from ProtonMail Mobile >>> >>> >>> On Wed, Jun 3, 2020 at 15:44, Greg Hellings <greg.helli...@gmail.com> >>> wrote: >>> >>> I will remind you >>> >>> 1) Windows builds of the utilities are not officially supported at all >>> 2) Builds of the utilities from any source other than SVN trunk are not >>> supported at all >>> >>> This problem falls into both categories and is, therefore, not a >>> supported situation that is likely to garner any attention. >>> >>> --Greg >>> >>> On Wed, Jun 3, 2020, 09:36 David Haslam <dfh...@protonmail.com> wrote: >>> >>>> http://tracker.crosswire.org/browse/MODTOOLS-104 >>>> >>>> Sent from ProtonMail Mobile >>>> >>>> >>>> On Wed, Jun 3, 2020 at 14:33, David Haslam <dfh...@protonmail.com> >>>> wrote: >>>> >>>> My Sword path is not in the part of the system that Windows guards like >>>> that! >>>> >>>> It's where any normal Windows user with the same name would have it. >>>> >>>> C:\Users\David\AppData\Roaming\Sword >>>> >>>> For my own convenience, I have subst s: <sword_path> as one of the >>>> several substitute drives made during startup. >>>> >>>> I never had such a weird problem with other module creation tools. >>>> >>>> Best regards, >>>> >>>> David >>>> >>>> Aside (especially for Tom): Eggshell™ is Sean Connery's favourite >>>> spreadsheet program. >>>> [image: image.png] >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Sent with ProtonMail Secure Email. >>>> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> On Wednesday, 3 June 2020 14:22, Tom Sullivan <i...@beforgiven.info> >>>> wrote: >>>> >>>> > David: >>>> > >>>> > I gave up on Microslop and Windoze years ago. So I am way out of date, >>>> > but even several years ago, Windoze would, for security reasons, >>>> restore >>>> > changed system files and delete foreign files unless certain settings >>>> > were made. C:\, was protected then, and maybe now. >>>> > >>>> > I think you got hit by Windoze is smarter than you behavior. Try cd to >>>> > your "my documents" directory and repeat. If you see a 3 files, then >>>> > you have a Windoze problem. You should be able to break your script >>>> into >>>> > simpler steps and fix things. >>>> > >>>> > Hope this helps. >>>> > >>>> > Tom >>>> > >>>> > Tom Sullivan >>>> > i...@beforgiven.info >>>> > FAX: 815-301-2835 >>>> > >>>> > >>>> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >>>> > >>>> > On 6/3/20 9:10 AM, David Haslam wrote: >>>> > >>>> > > I followed Timmy's sensible suggestion, which was something I'd >>>> pondered >>>> > > myself already. >>>> > > Now here's what I observed. >>>> > > Files lbc1646.dat and lbc1646.idx appeared /momentarily/ in the >>>> > > Make folder, but simply vanished when lbc1646.bdt finished being >>>> > > created. >>>> > > Does anyone have a plausible explanation for such bizarre behaviour? >>>> > > Were they moved to some unknown destination or simply deleted? >>>> > > Best regards, >>>> > > David >>>> > > Sent with ProtonMail https://protonmail.com Secure Email. >>>> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> > > On Wednesday, 3 June 2020 13:34, Timmy tim....@gmail.com wrote: >>>> > > >>>> > > > Hi David, >>>> > > > As Tom also mentioned, I run the command on linux, in your case, >>>> like >>>> > > > this: >>>> > > > ..\utils64\xml2gbs -fO ..\Import\OSIS\OSIS-lbc1646.fix.xml lbc1646 >>>> > > > Windows also can have issues if there are spaces in the path. I >>>> don't >>>> > > > know if your full path has any spaces, but you might want to try >>>> > > > running from c:\ directly, or some path that has no spaces. >>>> > > > >>>> > > > After command runs, the 3 files are in current directory. If it >>>> does >>>> > > > not work on Windows then there might be wins problem, not sure. >>>> > > > * >>>> > > > >>>> > > > >>>> --------------------------------------------------------------------------------------------------------------------------------------- >>>> > > > >>>> > > > Timmy Braun* >>>> > > > On Wed, Jun 3, 2020 at 6:23 AM David Haslam < >>>> dfh...@protonmail.com >>>> > > > mailto:dfh...@protonmail.com> wrote: >>>> > > > >>>> > > > Thanks Tom, >>>> > > > >>>> > > > The module name is [LBC1646] (as specified in my .conf file), and >>>> > > > that points to the right module path. >>>> > > > >>>> > > > This was the command in my CMD file, all of which are stored in a >>>> > > > folder called Make under my Sword path. >>>> > > > >>>> > > > ..\\utils64\\xml2gbs -fO ..\\Import\\OSIS\\OSIS-lbc1646.fix.xml >>>> > > > ..\\modules\\genbook\\rawgenbook\\lbc1646\\lbc1646 >>>> 2>..\\Log\\error.log >>>> > > > >>>> > > > NB. utils64 is a symbolic link to where I installed the Windows >>>> > > > edition of Sword utilities (x64 version). >>>> > > > Likewise, the Import folder is one I created some years ago. The >>>> > > > Log folder is similar. >>>> > > > >>>> > > > This command created the file called lbc1646.bdt in the right >>>> > > > place, but did not create the other two files. >>>> > > > And, yes, I've looked for them elsewhere too! >>>> > > > >>>> > > > So am I doing something wrong or is there a deficiency in the >>>> > > > Windows edition of xml2gbs ? >>>> > > > >>>> > > > >>>> > > > Best regards, >>>> > > > >>>> > > > David >>>> > > > >>>> > > > Sent with ProtonMail Secure Email. >>>> > > > >>>> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> > > > On Wednesday, 3 June 2020 12:57, Tom Sullivan >>>> > > > <i...@beforgiven.info <mailto:i...@beforgiven.info>> wrote: >>>> > > > >>>> > > > > David: >>>> > > > > >>>> > > > > You will have cd to a temporary directory xml2gbs as xml2gbs >>>> > > > just puts >>>> > > > > its output in the current directory, then copy files from that >>>> > > > temporary >>>> > > > > directory to your .sword library as below, along with your .conf >>>> > > > file. >>>> > > > > >>>> > > > > All three of those files are created simultaneously. >>>> > > > > >>>> > > > > After you copy from the temporary directory, you should have a >>>> .conf >>>> > > > > file in .sword/mods.d, (done manually), and then from your >>>> temporary >>>> > > > > directory: in .sword/modules/genbook/rawgenbook/somemodulename >>>> > > > the three >>>> > > > > files *.bdt, *.dat, *.idx. >>>> > > > > An images directory should be there also if there are images. >>>> > > > > >>>> > > > > This is Linux. I do not know what Windoze will do. >>>> > > > > >>>> > > > > Hope this helps. >>>> > > > > >>>> > > > > Tom >>>> > > > > >>>> > > > > Tom Sullivan >>>> > > > > i...@beforgiven.info >>>> > > > > FAX: 815-301-2835 >>>> > > > > ---------------------> It's apparent that the .dat and .idx >>>> > > > files are >>>> > > > > needed for the module to function aright. >>>> > > > > >>>> > > > > > When I tried to open the new module in Xiphos, nothing was >>>> > > > displayed. >>>> > > > > > So please would someone explain how I can make these two files >>>> > > > so that my new module will work correctly. >>>> > > > > > Best regards, >>>> > > > > > David >>>> > > > > > Sent with ProtonMail Secure Email. >>>> > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> > > > > > On Wednesday, 3 June 2020 11:18, David Haslam >>>> > > > dfh...@protonmail.com <mailto:dfh...@protonmail.com> wrote: >>>> > > > > > >>>> > > > > > > I have just used xml2gbs to create a Generic book module for >>>> > > > the first time. >>>> > > > > > > It created a module file with extension .bdt in the right >>>> > > > location. >>>> > > > > > > All Generic book modules I've installed from CrossWire also >>>> > > > have two more files in the module folder. >>>> > > > > > > One with extension .dat and one with .idx >>>> > > > > > > I have not found anything on our wiki that describes what >>>> > > > software tool is used to create these two files, nor an >>>> > > > explanation of what they are for. >>>> > > > > > > Please would someone enlighten me. >>>> > > > > > > Best regards, >>>> > > > > > > David >>>> > > > > > > Sent with ProtonMail Secure Email. >>>> > > > > > >>>> > > > > > sword-devel mailing list: sword-devel@crosswire.org >>>> > > > <mailto:sword-devel@crosswire.org> >>>> > > > > > http://www.crosswire.org/mailman/listinfo/sword-devel >>>> > > > > > Instructions to unsubscribe/change your settings at above page >>>> > > > > > >>>> > > > > > This email has been scanned by the Symantec Email >>>> > > > Security.cloud service. >>>> > > > > > For more information please visit >>>> http://www.symanteccloud.com >>>> > > > > >>>> > > > > sword-devel mailing list: sword-devel@crosswire.org >>>> > > > <mailto:sword-devel@crosswire.org> >>>> > > > > http://www.crosswire.org/mailman/listinfo/sword-devel >>>> > > > > Instructions to unsubscribe/change your settings at above page >>>> > > > >>>> > > > >>>> > > > _______________________________________________ >>>> > > > sword-devel mailing list: sword-devel@crosswire.org >>>> > > > <mailto:sword-devel@crosswire.org> >>>> > > > http://www.crosswire.org/mailman/listinfo/sword-devel >>>> > > > Instructions to unsubscribe/change your settings at above page >>>> > > > >>>> > > >>>> > > This email has been scanned by the Symantec Email Security.cloud >>>> service. >>>> > > For more information please visit http://www.symanteccloud.com >>>> > > >>>> > > sword-devel mailing list: sword-devel@crosswire.org >>>> > > http://www.crosswire.org/mailman/listinfo/sword-devel >>>> > > Instructions to unsubscribe/change your settings at above page >>>> > >>>> > sword-devel mailing list: sword-devel@crosswire.org >>>> > http://www.crosswire.org/mailman/listinfo/sword-devel >>>> > Instructions to unsubscribe/change your settings at above page >>>> >>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel@crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel@crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page