Crystal X - Discussion

Hi Kardo

I have download your File and click on the checkup Button and it did not work

 

Hello,

Thank you for your feedback!

False positive will be fixed and new Beta of Crystal X is out within 10 minutes.

Regards,
Kardo

 

Hello,

Can you please describe what happens when you click on Checkup.

When you click on Checkup then it should ask for admin rights if your Windows is at least Vista or newer.

I will release new Beta within 10 minutes and in this version is fixed minor bugs in Checkup feature. When new Beta is out you should try it again

Regards,
Kardo

 

Hello,

Crystal X 1.0.0.3 BETA Released

Thank you to all BETA testers who helped me with suggestions and testing!

Changelog:

New

¤ File name is visible during analysis
¤ Details link is visible after analysis [open results link via browser]
¤ Added Cancel button for analysis
¤ Added balloon tip for Checkup status [completed status]

Fixed

¤ Bug in File Manager [while adding file]
¤ False positive reported by users
¤ Not responding during Checkup first step [should work normally now]
¤ Bug in Analysis [occured on certain systems]
¤ Minor bugs in Checkup

Download: -http://crystalsecurity.uk.to/downloads/Crystal%20X%201.0.0.3.zip

How-to-run

1. Download Crystal X zipped file from download link.
2. Extract downloaded .zip file with some extraction tool (e.g. 7-zip or WinRAR)
3. Double-click (run) extracted executable file of Crystal X (Crystal X.exe)

Note

.NET Framework 4 is required.

Regards,
Kardo

 

Hi Kardo

Can you check it

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.IO.PathTooLongException: Der angegebene Pfad und/oder Dateiname ist zu lang. Der vollständig qualifizierte Dateiname muss kürzer als 260 Zeichen und der Pfadname kürzer als 248 Zeichen sein.
bei System.IO.PathHelper.GetFullPathName()
bei System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
bei System.IO.Path.GetFullPathInternal(String path)
bei System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath)
bei System.Security.Util.StringExpressionSet.CreateListFromExpressions(String[] str, Boolean needFullPath)
bei System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
bei System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String path)
bei System.IO.FileSystemInfo.get_FullName()
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.ListFiles(String directoryPath)
bei Crystal_X.Form1.Settings()
bei Crystal_X.Form1.Form1_Load(Object sender, EventArgs e)
bei System.Windows.Forms.Form.OnLoad(EventArgs e)
bei System.Windows.Forms.Form.OnCreateControl()
bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bei System.Windows.Forms.Control.CreateControl()
bei System.Windows.Forms.Control.WmShowWindow(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ContainerControl.WndProc(Message& m)
bei System.Windows.Forms.Form.WmShowWindow(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
Crystal X
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.2.
CodeBase: file:///C:/Users/Alexander%20Robrecht/Desktop/Crystal%20X.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18014 built by: FX45RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.17929 built by: FX45RTMREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

 

Hi Kardo

Trying the latest beta, and in relation to what Mops21 said I note that from the moment that one presses 'Check Up' to the time that Crystal X starts 'classifying' i.e., the app shows what files/executables it is checking...and I am supposing that in that time it is possible that someone would think that nothing was happening, etc.

I am not sure what Crystal X is doing in that 'gap' but may I suggest that the status is changed to something like 'Preparing to Check' or something similar so that the user understand that work is being done/the app is acting normally, etc?

BTW, the FP on CrystalX.exe has been cured but still getting one for MCShieldSetup.exe (which I am sure is incorrect), etc.

Regards



Balders

 

Hi

When i click on checkup it Hangs.

My System is Windows Vista Home Premium 32- Bit

 

Hello,

Thank you for your feedback!

Yes, balloon tip will be added so user will see following: "Status: Collecting system information....Please wait" and after that Crystal X window appear with checkup progress.

Checkup detection (malware & false positive) will be improved with newer versions of Crystal X.

Regards,
Kardo

 

Hello,

Thank you for your feedback!

Your problem will be solved with next version of Crystal X.

Regards,
Kardo

 

Hi

Thank you very much

Can you add a about your Programm Info

 

Hello,

Happy New Year!

Crystal X 1.0.0.4 BETA Released

Thank you to all BETA testers who helped me with suggestions and testing!

Changelog:

New

¤ Install updates automatically [settings]
¤ Checkboxes for objects [checkup]
¤ Button Clear log [events]
¤ Added balloon tip for Checkup status [first step]

Fixed

¤ Greyed out Details [analysis]
¤ Bugs in Checkup
¤ False positives [checkup]

Improved

¤ Checkup detection

Download: -http://www.crystalsecurity.uk.to/downloads/Crystal%20X%201.0.0.4.zip

How-to-run

1. Download Crystal X zipped file from download link.
2. Extract downloaded .zip file with some extraction tool (e.g. 7-zip or WinRAR)
3. Double-click (run) extracted executable file of Crystal X (Crystal X.exe)

Preview

Information: preview of Crystal X 1.0.0.4 BETA

Video: -http://www.youtube.com/watch?v=b4mcmD0pIvU&feature=youtu.be

Note

.NET Framework 4 is required.

Regards,
Kardo

 

Hi Kardo

What can you say about my Post Nr. 30

Can you add a about your Programm Info

 

Hello,

Your issue should be fixed with version 1.0.0.4 BETA.

I also added preview video of Crystal X 1.0.0.4 BETA.

You can watch it from here: -http://www.youtube.com/watch?v=b4mcmD0pIvU&feature=youtu.be

Regards,
Kardo

 

Hi Kardo

Can you add a about your Programm Info

 

Hi Kardo

My issue is fixed now it is gone it worked for me

Thank you very much

 

Hi Kardo

No FPs detected with this build when compared to previous builds. That is good but when checking asetup file with one of the 4 choices I got a program error and Crystal X had to close (standard Windows 'Close program...' prompt). Am currently trying to reproduce and will post back as and when I can.

regards



Baldrick

 

Hello,

Good that your issue is fixed for now.

Hmm, what information you mean?

Please send PM.

Regards,
Kardo

 

Hello,

CAMAS problem is confirmed and will be fixed with next version.

Regards,
Kardo

 

Hi Kardo

OK, thanks. Have just reproduced the issue for CAMAS site...so we are aligned...which is good.

Happy New Year.

Regards



Balders

 

Hello,

Thank you for your reply.

I just performed some tests with CAMAS and figured out what is causing crashing problem.
I don´t know why but for some reason CAMAS show result that file is unexecutable (even when file type is application - .exe) and that´s why test fails.

Now, when file is executable for CAMAS and test is successful, then there is no problem with result.

This issue is easy to fix (in next version if test fails...Crystal X show result C: unexecutable).

Thank you!

Happy New and Successful Year for You.

Regards,
Kardo

 

Hi Kardo

Thanks.

Have done some further testing and of the 15 executables that I have tried (which included setups, uninstalls, 'proper' .exes, etc) NONE have worked with CAMAS but all have worked with the 3 other sites.

I am wondering if there is something wrong in terms of what is actually submitted to CAMAS, i.e., format of submission, parameters, etc.?

Also am not sure that if test fails showing result as 'C: unexecutable' is actually the right thing to do as the apparently 'unexecutable' executables are in fact executable on my PC.

My suggestion would be to report the CAMAS check as 'Failed' or something similar so that the user can then check with another site, etc.

Just my thoughts...for what they are worth.

Regards



Balders

 

Hello,

Thank you for your feedback!

Hmm, you may also try these same executables via browser-website.

I just tried 4 files and 2 of these files failed to test.

Your suggestion will be implemented.

Any feedback and suggestion is welcome.

Regards,
Kardo

 

Hello,

Crystal X 1.0.0.5 BETA Released

Thank you to all BETA testers who helped me with suggestions and testing!

Changelog:

New

¤ File info [analysis]

Fixed

¤ Bug in CAMAS result [process failed] [analysis]
¤ Program crash during CAMAS result [analysis]

Download: -http://www.crystalsecurity.uk.to/downloads/Crystal%20X%201.0.0.5.zip

How-to-run

1. Download Crystal X zipped file from download link.
2. Extract downloaded .zip file with some extraction tool (e.g. 7-zip or WinRAR)
3. Double-click (run) extracted executable file of Crystal X (Crystal X.exe)

Note

.NET Framework 4 is required.

Regards,
Kardo

 

Hi

I mean Versions Info

 

Hi Kardo

You could also put a link to your website, as and when the app is out of beta, etc.

BTW, tested the latest beta and the CAMAS-related fixes are peachy

Regards


Balders