You didn't said about the processor. still based on your question,
Win 7 (Any version except Basic) x32 bit can not use more then 3.25 GB of RAM (even if you have 16 GB RAM)
while Win7 x64 bit can use any amount of RAM, So as you have 4GB and if you want to use full of it you have to load Windows 7 x64bit - or any O/S x64bit it may Vista/Win8 Anything.
Performance : x64bit will support almost every application that developed for a x32bit machine. And there will be no performance issue. I m using x64bit in my Home PC (that have 8GB) and in my Laptop (4GB)
Only drivers will not support x64bit if they made for x32bit.
Here is a link where you can get all Laptop and other components drivers in one page.
Hi, I'm trying to interface a gap sensor with pic micro-controller but I'm not winning. I wanna design a barcode reader. Can anyone help me with the circuit that I can use to interface the gap sensor with a PIC16F series please.
I've always wondered if it was possible to take an old 6502 or 65816 microprocessor, which run in the 1-3 MHz range, and get it to run in the GHz range. I know I can run an emulator of an Apple II machine at high speed, but has anyone ever done it with the real hardware?
Something about a blazing fast computer with a simplified instruction set (only 256 opcodes!) that really appeals to me!
Simplistically speaking, so long as you can get rid of the heat you're going to generate by running at higher clock speeds, yes, it's possible, but only to a certain limit. Internal timing structures will eventually prohibit you from going faster.
But, you have a bigger problem. The supporting chipset for the CPU will not be able to keep up with your higher clock speeds and you'll run into all kinds of timing problems there too, probably much sooner than you run into problems with the CPU alone. The stuff simply wasn't designed to go that fast.
Oh, I wouldn't be surprised if you needed a liquid nitrogen cooler to get rid of the heat you'll generate by clocking a 6502 into the GHz range.
Running an emulator is VASTLY different from running actual hardware.
These CPUs are heavily CISC in nature, and originally had been implemented (supposedly) as multi-cycle FSMs. In order to get the modern high clock rates and high IPCs, such CPUs have to be reimplemented as RISC, superscalar pipelines, adding a complex instruction decoder (as in x86) to get away from CISC restrictions. It does not make much sense to do so - much easier to synthesise a simple MIPS core of a comparable complexity.
Hmm...it just occurred to me, this might be the appropriate place for me to post.
Thing is, I've made a USB board called PeekyPokey with an API so that you can use .NET languages such as C# for interfacing with electronics stuff like relays, RFID tag readers, tactile buttons, rotary encoders, keypads, sensors, servos and things like that.
The API also comes with an extensive toolkit containing classes for the PC side of things too - like a built in webserver, gamepad drivers, virtual keys, MIDI interface, a generalized HID interface and so on - things you can use to control electronic devices.
In essence, PeekyPokey has 8 general input/outputs, a virtual COM port, 3.3V/5V power supplies and kind of brings Windows PCs and electronics together in pretty much the same way IOIO does for Android.
The PeekyPokey board targets programmers curious of embedded electronics programming and hardware interfacing. The whole idea is to play, explore, learn and have fun with electronics.
This is just to let you guys know it's there and love to hear what you think!
NOTE: I'm not selling the boards, I'm just the creator.
As far as I know that is a direct signal straight from the hard drive itself, which is also directed to an LED when you have a drive installed in a removable tray. This might be an oversimplification since signals from multiple drives are combined and routed by the controller to the motherboard pin.
So, if you follow midnight_matt's lead, you can argue it is a driver issue of sorts, caused by the Intel Rapid Storage Technology thing that for some reason is polling the CD/DVD drive constantly.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
I'm pretty sure the issue was coming from Win 8. Here's how I know:
I discovered that Win 8 was not seeing my DVD drive. So I found a fix for that on MSDN that involved adding a registry key and rebooting.
Voila! Not only did Win 8 start seeing my DVD drive, but the hard drive light was back to normal!
The difficult we do right away...
...the impossible takes slightly longer.
Last Visit: 20-May-19 17:29 Last Update: 20-May-19 17:29