- #DARK BASIC PRO EXPORT AS EXECUTABLE INSTALL#
- #DARK BASIC PRO EXPORT AS EXECUTABLE PATCH#
- #DARK BASIC PRO EXPORT AS EXECUTABLE CODE#
- #DARK BASIC PRO EXPORT AS EXECUTABLE PC#
- #DARK BASIC PRO EXPORT AS EXECUTABLE FREE#
BSP WW2 characters with over 1000+ frames per limb takes approx 1 min to process per model.
#DARK BASIC PRO EXPORT AS EXECUTABLE CODE#
***22Nov17 - Version 1.7 now released to SegAutoWelder purchasers - exporter code optimized for matrix format animation frame data which now speeds up that side of the process. This version also has the additional progress bar so you know where the program is at and not left in the dark
#DARK BASIC PRO EXPORT AS EXECUTABLE PC#
1 T341 char processed in 22 seconds on my PC (might be faster than Fragmotion possibly). T341 models with 5501 anim frames per bone (around 27 bones).
I have used their products off and on for over 6 years now, so I seriously doubt that they've turned into a malware company.***29Nov17 - Version 1.7.2 now released - extremely fast exporting of X files especially characters e.g.
#DARK BASIC PRO EXPORT AS EXECUTABLE FREE#
One other thing, I also ran these test with a free version that they have on their site (I use a paid registered version, but I wanted to see if this also occurred with their free version, which it does.) It would probably be more helpful to you to just acquire their free version and observe the results on your local systems. Which I can do if it would be helpful to you. I would have to set up a third virtual machine to build an "Ignored" version of the executable. Unfortunately, once I selected quarantine all future builds of that same project resulted in the same "quarantined" file. I am including one of their sample projects built on the non Malwarebytes VM and a quarantined version from the other VM. However, it is clear that the two applications are incompatible with each other and that I will have to create my builds on a system without Malwarebytes installed. I originally thought that any executables that I generated would trigger a Malware alert on the target systems. This turns out not to be as important an issue to me as I originally thought. I then scanned the files with MalwareBytes and both the zipped and unzipped files tested clean. I then zipped and copied both the uncompressed and the compressed versions to a common drive, shut down the second VM and restarted the first VM. On the second VM I compiled and built the same project. But regardless of which response I choose from the Malwarebytes dialog, the file no longer tests positive on any future scans. Furthermore, I observed that selecting "Disable protection" or "Ignore" immediately results in the corruption of the executable files "Version properties" (Right click on the executable, select Properties, select the Version tab - At least the Comment and Company properties will be filled with "2"s and "3"s.) Chosing "Quarantine" results in a corrupted application icon.
If I compile any of the sample projects on the first VM it will trigger the MalwareBytes alert. On the first machine I also installed my registered version of MalwareBytes and turned on protection.
#DARK BASIC PRO EXPORT AS EXECUTABLE INSTALL#
I created two fresh clean install virtual machines with only Windows XP sp/3, Microsoft Security Essentials, DarkBasic Pro. Ok, after much research and many clean virtual machine trials, it seems that there is something in the compile process itself that triggers the Malwarebyte alert. I am not getting any detection here, I am going to need an exact path from the detection as it appears in our protection module warning. Has this been reported before? (I couldn't find a record searching through the forums or Googling it.) Maybe a "legitimate Trojan" (oxymoron?) exists that was built with DarkBasic Pro and MalwareBytes is detecting the same run-time signature, I'm not sure. I don't know if this has existed for some time or not. I then proceeded to build one of the example projects and was immediately presented with a MalwareBytes alert.Įvidently, there is something in DarkBasic Pro's run-time environment which is now being flagged as a Trojan.Agent in the latest version of MalwareBytes DB (3664).
#DARK BASIC PRO EXPORT AS EXECUTABLE PATCH#
After the 7.4 patch was installed, I scanned the install directory one more time and all was clean.
I then applied the 7.4 patch after scanning it without incident. Ran a complete scan and found no other issues. I quarantined the executable without running it and removed it from my system. I then installed the CD again (a very early 1.0 version), everything installed fine, but when I opened the one example project directory that had a pre-compiled executable, MalwareBytes immediately flagged the executable. This time I scanned the CD before installing, no problems. I then proceeded to uninstall DarkBasicPro, clean my system and start over. Malware blocked the executable and quarantined it. I updated to the latest version 7.4 and attempted to run/compile one of the examples. Yesterday I dusted off my DarkBasicPro CD and did an install without any issue. It appears that any executable file created with the DarkBasic Pro (development environment is generating an alert from my MalwareBytes protection.
0 kommentar(er)
