|
1. Most information ca be provided by the systeminfo command.
2. Run the programs in a batch file, piping their output to whatever repository you want.
|
|
|
|
|
Hi
Imagine a user-mode process is communicating with a driver using IOCTL (DeviceIoControl).
1.) I'd like to learn if there is a way to find if a process is communicating with a driver.
2.) In which cases would it be impossible to find it? For example there are multiple ways that a process can communicate with a driver: IOCTL, shared memory, netlink, system calls, netlink Sockets etc.
|
|
|
|
|
1. You would need to use Windows hooking (Google will find you details).
2. Maybe not impossible, but extremely difficult. You would probably need a good knowledge of windows drivers.
|
|
|
|
|
Thurrott: It's "Game Over", "UWP will disappear" - MSPoweruser[^]
"As far as I can see, the future of native applications on Windows has very little to do with the Microsoft Store. However, I do not expect the store to disappear. But I expect that UWP will disappear, especially on the Windows desktop. And that the Microsoft Store remains irrelevant to most users and most developers."
This sums up my opinion of UWP pretty much since its introduction. Thoughts? Any fans of UWP over "legacy" WPF desktop app development?
|
|
|
|
|
FUD.
Surface sales are exceeding all expectations. Most apparently not even being moved out of "Z" mode (i.e. "Store").
Windows store is getting rid of "Books" ... good?
Learn WPF or UWP; i.e. XAML.
Create Net standard libraries for inter-op.
Avoid Xamarin for now unless you like big buttons, lame list controls and tiny real estate (and long compiles).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
The thing you have to remember about Thurrott is that he's aiming to make money from clicks so titles like this are massive clickbait. UWP will not disappear - for some reason, he completely failed to understand what all the announcements at Build were wrt UWP.
This space for rent
|
|
|
|
|
hi
i have a laptop Dell N5110 whith :
Intel core i7-2570qm cpu 2.20 ghz
ram 8 gig
Intel hd graphic 3000 and nvidia gforce gt 525m
now i want to installing new windows but i don't know which is good for me : windows 10 or windows 8.1
can you help me for choice a windows with good performance for my laptop
tanks
|
|
|
|
|
Windows 10 will allow you to run the "newer" software apps which Windows 8.1 doesn't (e.g. MS Edge; 3D Paint).
However, you won't have a "good" experience with the new virtual / mixed reality apps which require a more powerful graphics cards than what your laptop has.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Your only choice is Windows 10. You can't buy Windows 8.x anymore.
Also, Windows 8.1 went into "extended support" in January this year. It now only receives security patches and will only do so until January 2023.
|
|
|
|
|
|
hi
i have a laptop Dell N5110 whith :
Intel core i7-2570qm cpu 2.20 ghz
ram 8 gig
Intel hd graphic 3000 and nvidia gforce gt 525m
now i want to installing new windows but i don't know which is good for me : windows 10 or windows 8.1
can you help me for choice a windows with good performance for my laptop
tanks
|
|
|
|
|
I think your system is good enough for Windows 10. Go for Windows 10. You will have the latest and most stable operating system.
I cannot think of any specific reason for Windows 8.1.
|
|
|
|
|
Hi all,
I'm trying to schedule a backup operation at system shut down.
I've tried EaseUs and AOMEI programs. Both state that this works.
If I shut down the computer using the start menu nothing happens.
If I call the command "shutdown /s /t 0" from the command line both work well and the backup gets performed.
This makes me think there is a difference between the shutdown in the start menu and that command line.
Is there a way to configure the start menu shut down button to mimic that command line?
Thank you all.
|
|
|
|
|
Found it...
If you are using windows 10, then it is possible you have selected "fast boot" in the power options (it comes active by default).
Disselecting it solved the issue.
|
|
|
|
|
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP.
When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible).
See Bad Start Menu[^]
There are lots of error entries in the Event Log like:
EventLog Example 1[^]
EventLog Example 2[^]
EventLog Example 3[^]
EventLog Example 4[^]
The program, itself, seems to operate correctly!!!
Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10.
To my surprise, the symptoms were the same! 
(I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.)
For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications.
I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why.
Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo"  to use, etc?
Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
Matt T Heffron wrote: but with right mouse click a simplified, text only menu appears
That is exactly what one expects to see with right-click on the start button. What do you actually see on a left click? As to the event log entries, how do they relate to your application?
|
|
|
|
|
Left click does nothing at all.
(I had never done right click on the Win 10 start button!)
Some of the menu items also do nothing when clicked.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
modified 8-Mar-18 15:53pm.
|
|
|
|
|
The event log entries suggest that your DCOM permissions are broken:
When this issue occurs, error events that resemble one or more of the following may be logged in the System log:
Event ID 10022
Source: COM
Description: The machine-default access security descriptor for the COM Server application D:\exchsrvr\bin\mad.exe is invalid. It contains access control entries with permissions that are invalid. This security permission can be corrected using the Component Services administrative tool.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks!
So the next question will be:
How do I figure out what part of the program installation wreaks havoc with the DCOM permissions in such a way as to have no (apparent) effect on a Windows 7 system, but is a disaster when upgrading to Windows 10?
(And clobbers Windows 10 directly, when installed onto Windows 10.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
This sort of problem is going to be painful to diagnose. I'd suggest:
- Start with a fresh Win7 VM;
- Open
dcomcnfg, and look at the various settings under "My Computer ⇒ Properties ⇒ COM Security"; - Install the application;
- Look at the COM Security settings again, and try to work out what's changed;
- Upgrade to Win10;
- Look at the COM Security settings again, and compare to the values from before the upgrade;
(You might need to do this from a remote PC if you can't open dcomcnfg on the upgraded box.)
Alternatively, you could use something like Process Monitor[^] to monitor the installation to see what it's doing.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
This is a "3rd party" product that you do not have the source to?
Not worth the trouble, IMO.
It could be anything, starting with Windows Update reversing every "retro" driver update you might make when you're not watching.
I remember one upgrade in particular ... Robotron 2084 "over-clocked" and became unplayable. Sad.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
This is a "3rd party" product that we OEM as part of some of our products.
(Much "core" functionality, not just an added-on library/control.)
We have recently licensed the source, but the installer is using a very old version of InstallShield. (XP-era)
Modifying the installer to work with Windows 10 is another project. I'm just trying to figure out how to upgrade my development laptop, that already has this product installed, from Windows 7 to Windows 10, without getting the corruption I've seen. (Secondarily, knowing this would be useful in case a customer wants to do the same upgrade.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
Some older programs try to force Windows "Classic" mode; that will do weird things.
Some programs must compile to x86 (for 64); cannot run mixed.
Inno setup handles all my setups; x86 / 64; EF; SQL Server. (XP; 7; 8.1; 10).
I would "move" the project to a Windows 10 machine; not go Win 7 to 10 with the project on the machine.
(XP was always nice ... by itself).
(The most I usually do for any machine is upgrade from "home" to "pro". After that, it's a new machine).
(I've developed on 8.1; for 7; that runs on 10; VM Box good; Hyper-V not so much - screen artifacts).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
modified 9-Mar-18 21:49pm.
|
|
|
|
|
Redirects to spam.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I need to create a self-signed certificate and private key on a new installed win7x64 sp1. For this, I installed the Windows SDK and Driver Kit 7.1.0 updated the framework to 4.5. Then, according to the instructions, I need to execute the first command on the command line - "cd C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin" then run the second command - "makecert -r -sv C:\WinItProDriverCert\WinitproDrivers.pvk -n CN="Winitpro" C:\WinItProDriverCert\WinItProDrivers.cer" But when I try to run the second command, I get an error :
"" Error: Unable to create file for the subject <' C:\WinItProFriverCert\WinItProFrivers.pvk'"
Error: Can't create the key of the subject <' C:\WinItProFriverCert\WinItProFrivers.pvk'"
Failed ""
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
