|
Thanks Think I will scrub the USB External Hard Drive
Then create a Bootable Media do a Full BackUP and Incremental every 2 months
Might try to save the current USB External Hard Drive to another USB Hard Drive just encase
Not sure what software to use for that procedure will do a little Duck Go search
|
|
|
|
|
UPDATE: I just contacted DigiCert support, and the rep couldn't figure it out either. He said everything looks OK with my certificate, so he escalated it to their development team. I might hear back from them on Monday.
I have a Windows Filtering Platform driver that I have signed with a DigiCert EV code signing certificate.
I submitted the package to the Windows Partner Center as a hardware submission, and it was successfully signed by Microsoft. I chose "Test Signing" and I checked the boxes for every listed version of Windows that was not ARM based.
So when I run this command:
signtool verify gsllc.sys
It gives the following response:
File: gsllc.sys
Index Algorithm Timestamp
========================================
SignTool Error: A certificate chain processed, but terminated in a root
certificate which is not trusted by the trust provider.
Number of errors: 1When I attempt to load the driver into Windows, the event log shows the following error:
The gsllc service failed to start due to the following error:
A certificate was explicitly revoked by its issuer. My certificate is only days old, and it hasn't been revoked according to DigiCert.
Anybody have any idea what could be wrong here?
The difficult we do right away...
...the impossible takes slightly longer.
modified 18-Feb-24 10:25am.
|
|
|
|
|
Richard Andrew x64 wrote: root certificate
Well the error means nothing is wrong with your actual cert.
But certs have an parent chain (best phrase I can think of) and it doesn't like one of the parents.
I didn't google but I am rather certain there is probably a tool that will tell you what the chain is.
I will say that probably won't help with your problem since it is likely nothing you can do with a parent. But maybe something to so with how you created the cert in the first place. This supposes of course that just looking at the chain gives you an idea which one is a problem in the first place.
|
|
|
|
|
jschell wrote: But maybe something to so with how you created the cert in the first place
I'm impressed with the likelihood that you actually meant to use the word "so" to replace the word "do" in this sentence, so I think for a second, "what other substitutions can I make here that would still make sense and lend credence to authority and I came up with "io" ... lexicographers of the world UNITE! 
|
|
|
|
|
Agreed. The signtool.exe can show the complete chain from the root to your certificate.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Hello,
I'm having trouble understanding the INF file(s) that I must submit for microsoft test driver signing.
If I'm submitting a driver for both of the x86 and x64 platforms, must I submit a separate INF file for each version of the driver?
SOLUTION:
The same INF file can be used for both x86 and x64 binaries.
The difficult we do right away...
...the impossible takes slightly longer.
modified 17-Feb-24 15:15pm.
|
|
|
|
|
A transistor is a “device” in which a high power current acts as a switch that can turn on and off the circulation of a lower power current. The later then may act as a switch in another transistor. To get this working you need to amplify the incoming low power current from the first transistor to make it a high power current that will pass through the second transistor is this correct?
|
|
|
|
|
Calin Negru wrote: a high power current acts as a switch that can turn on and off the circulation of a lower power current
Rather the other way around: A low power current can switch a higher power current on and off. Or, in analog transistors: Turn up or down the high power current proportionally to the controlling low power current. So the purpose of the transistor was to amplify the signal.
In digital circuits, you really do not need this amplification. The output from the first transistor need only be strong enough to turn the second transistor on (i.e. opening it to let a signal through) or off.
Under special circumstances, where the output of the first transistor is distributed to a whole row of second transistors, e.g. located on the row of plugin cards on a mainboard bus, the output signal must be strong enough to feed everyone of them. You don't see much of that any more: In the days of S100, ISA and MCA buses, you could plug 4-5-6-7 cards into a bus, side by side - the bus was like an AC power strip, delivering signals to a lot of recipients. You don't see much of that any more, partly because lots of what once required a large extension card now is provided on the CPU (or supporting 'chip set'), and partly because new bus standards have reduced the maximum 'fan out', to reduce the requirements for the bus electronics. Actually, lots of what we today refer to as 'bus' interconnects are really one-to-one signal lines.
(For the pedantic ones: It still isn't wrong to call it a 'bus': (Omni)bus means no more than 'For everyone'. In the days when the COM and LPT ports were used for 'everything', they were '(omni)busses', linguistically speaking.)
But talking about bus fanout and that sort of thing are special cases. Within a CPU, the current delivered from the output of a transistor is always enough to drive the input of the following transistor(s), even if there might be two or three of them receiving the same signal.
|
|
|
|
|
trønderen wrote: Or, in analog transistors:
I'm one of the pedantic ones. 
A transistor is a transistor. There's no analog transistor and no digital transistor, it's a transistor.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
OK, you are certainly right about that.
Also: Turning an ordinary light switch 'off' doesn't create an absolute insulation between the poles of the switch. The air gap just increases the resistance. A sufficiently high voltage may be able to cross that air gap.
Certainly: That kind of voltage would also be able to do wonders to your PC and other semiconductor eqipment.
|
|
|
|
|
trønderen wrote: That kind of voltage would also be able to do wonders to your PC
Not to mention flammable materials as well.
|
|
|
|
|
Thank you for your answer
> Rather the other way around
In that case doesn’t the output power of the first transistor need to be reduced? To create Boolean logic you need low power to act as a switch on the second transistor
modified 14-Dec-23 7:38am.
|
|
|
|
|
Digital transistors are not built for amplification. Essentially, the signal being controlled is at the same level as the controlling one. The control consists of either let the controlled signal through, or to stop it. (Sort of like the main valve to turn on/off the water supply to your house: It is either open or closed, not intended to be in any intermediate position.)
Like a water flow: If you open a valve completely, you won't have an infinite water flow, only as much as the source will supply. Same with transistors: A fully open transistor lets through whatever wants to get through, but in a digital circuit, that is not much more than the controlling signal.
Both the controlling and the controlled signal are low power. In a modern CPU, such as an x64 CPU, that is really low power! I willingly admit that I do not know how low, but would be curious to know! Even if could have gotten access to the transistor (which is completely impossible inside the CPU) my multimeter would not be able to measure it. Not by several orders of magnitude.
|
|
|
|
|
The simplest transistor to understand is the MOSFET used in most computer logic circuits.
The name describes the construction and how it works 😋
Metal-Oxide-Semiconductor is a thin aluminium on a thinner glass layer on a doped silicon surface. The doping impurities change the silicon's behaviour.
The FET part of the name is Field Effect Transistor. When a voltage is applied to the thin metal layer (gate) the charge acts across the insulating glass layer to pull carriers to the surface of the silicon, making a greatly more conductive channel for current at the surface.
A very small amount of power to charge the gate can control much larger currents in the underlying semiconductor.
|
|
|
|
|
You can also make a transistor from a crystal and two needles 
I guess that even software people have seen the classical transistor symbol used in circuit diagrams: A circle enclosing two slanted lines (one with an arrowhead), one from each side onto a bar, and a third line down from the bar; that is the control signal, steering how much current it let through from one needle to the other. The symbol is is a stylized drawing of the crystal and the two arrows. (For FETs the symbol is slightly modified; the lines are not slanted.)
I have been with semiconductors for so long that I have been thinking of crystal transistors as something they used two generations ago. So I was surprised to discover that you still can buy them, in a lot of varieties; they are often preferred in certain high frequency radio application. These are individual transistor components, usually in a sealed glass capsule. You wouldn't build a computer from them
|
|
|
|
|
|
I've been grappling with a frustrating issue lately and thought I'd seek some advice from this knowledgeable community. The problem at hand is that I'm unable to write to my NTFS-formatted external hard drive when it's connected to my Mac.
Here's a bit of background: I've been using this NTFS-formatted external hard drive primarily on a Windows PC. However, now that I'm a recent Windows-to-macOS switcher and working on my Mac, I find myself unable to add or edit files on this drive. I need to collaborate on some documents, and it becomes a bit of a headache.
After some research, I'm aware that macOS doesn't offer native write support for NTFS drives. Formatting to exFAT is an option, but it means moving all my data somewhere else temporarily, which led me to consider third-party solutions. One NTFS for Mac solution that's come up is iBoysoft NTFS for Mac. It claims to enable full read-write access to NTFS drives on Mac, but I wanted to gather some insights and experiences from the community here.
Has anyone been through this before? If so, how did you resolve it? If you've tried iBoysoft NTFS for Mac or have alternative suggestions, please do share your thoughts and experiences. I'm eager to learn and resolve this problem.
Thanks a bunch!
|
|
|
|
|
No idea.
But I will note that I had to read your entire post to figure out your real question. And read it twice just be be sure. Certainly not what I expected from the subject line.
What you actually are asking is ...
'Have you tried iBoysoft NTFS? If so did you like it? Would you suggest any alternative?'
|
|
|
|
|
Googling ntfs for mac produces lots of hits, including this one 6 Best NTFS for Mac Software in 2023 [Free and Paid]
All I can recommend is that you take a look at some of the reviews and choose what you think will be best for your use case.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
A memory pcb piece that comes mounted in a mother board memory slot has only about 100 pins. 4 Kilobyte of memory is a thousand ints on a 32 bit machine. How do you read or write a thousand ints through a bottleneck of 100 pins? Thank you
modified 21-Oct-23 10:20am.
|
|
|
|
|
One by one. Or, I believe, two by two for the current DDR generations (64 bits data bus).
Actually, current DDR memory generations have up to 288 pins. The CPU presents an address on one set of pins (on some memory types in two pieces, first the high order bits, then the low order bits), fires a 'read' signal, and the selected data bits come flowing out on the data pins. Or the CPU both presents the address and the data and fires a 'write' signal that reads what data the CPU presented into the addressed location.
|
|
|
|
|
Why is that so hard to understand? Think of it in terms of reading/writing one word at a time. In your case, 32-bits. That easily fits in a hundred pins, though I don't remember any memory modules with that pin count.
There were 72-pin SIMMs that handled 32-bit transfers, and that jumped to 168-pin DIMMs with a 64-bit transfer.
Besides power, ground, and control pins, you only need 1 pin per data bit and 1 pin per address line, so it's really not hard to understand.
Anandtech RAM Guide[^]
|
|
|
|
|
Thank you I understand. On visual inspection the pcb itself appears pretty simple, my guess is that simplicity is deceiving.
|
|
|
|
|
A cpu has a lot of pins. What are they meant for? Do they have a general purpose usage or does the processor have specialized groups of pins where each group talks to certain type of resource on the motherboard (video adapter, sound board, etc)
|
|
|
|
|
Go to the chip manufacturer's web site and get the datasheet.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
