[Bug 46643] BelarcAdvisor.exe crashes as first run on Wine and fresh install of Linux Mint 19v1 Tessa x86 AMD64

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46643

--- Comment #4 from Alexandra Crawford <arclite7 at gmail.com> ---
Hello Louis Lenders, I thank you for your clarification. I hope I can provide
some help in response to your questions and yes the Automagic was not expected,
thank you, it is surprising it got so far considering the following functions,
not benchmarking but a complete system audit, including windows internal system
references to a complete, optionally downloaded to date, index of hierarchical
(ntdw Canonical) patches and updates (what a surprise!).

So with the above download of the complete index to a Windows native internal
index of applied patches and updates before checking the Windows registers of
all equipment and software including license numbers, this audit is sufficient
to recover all license keys and numbers effectively before re-installing
"Windows" after the dreaded blue screen of permanent hive retirement.

I think Belarc(tm) represents the most thorough check of Windows own registers
of hardware and software such that Wine will need to correspond with a complete
emulation of a "present Windows, XP, 2000, NT, Vista, 7, 8, 10 view of itself, 
its underlying hardware system as well as all correctly registered and licensed
applications" in order for Belarc to populate a complete set of indexed HTML
pages into and about that system, its hardware, software and its resources,
i.e. links to Microsoft, software houses and hardware manufacturers web pages.

I  do suggest you try out the free version on a Windows system with at least
some patches installed! I like Belarc since I am able to use this free resource
to effectively document all my system details. If on the other hand I am
responsible for company IT infrastructure, this was and perhaps still is when
equipped with licensed networking tools, the fastest method of knowing what
your desktops and laptops are comprised of and that your Windows are not
damaged, broken or currently insecure? Better to know than to rely on the
concept of what a machine is from past invoices? I worked within a large
corporate where I observed machines being delivered without AV. A network worm
became established shortly afterwards and my desperate emails to IT had been
ignored? The worm apparently had the resources to discover all the unprotected
machines connected to the internal corporate network. It took a Microsoft task
force to clear the corporation with several million £UK in lost business
revenues. The reliance on an unverified paper view, i.e. supplier invoice
description, of what was going on lead to the departure of a key executive
member. Worms aka rootkits are now well established security issues just as a
lack of understanding of how they become established and what to do to prevent
code from being introduced either at boot time or during system use. All stuff
you already know.

Is there anything else you need from me?

Wishing you well and looking forward to being able to Belarc(tm) audit my
(Linux) system, virtual Windows view only and or actual Linux system too?
Personally I would look for an interim cooperative deal to realise your result!
But to push the Belarc authors to recognise and produce a Linux audit too and
how? Otherwise you would choose to capture this corner of the marketplace? I
mean you have to pull a couple of levers, and NDA's. Its down to honest hard
work after all? What is the equity at stake, would they bite to get it???

Till then!

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.