| Last online: 04.25.2017
Zitat von Extranick im Beitrag #10
Can not. We have application software that is licensed to XP. It's a few tens of thousands of dollars. That's why I'm trying to find a way for XP.
And where is the problem with XP in a virtual machine? It's still XP inside Windows 7/8/10.
Your "tens of thousands of dollars" worth application software would still run on XP.
Zitat von Fernando im Beitrag #39
Thanks for your explanations and advices, but I neither have the time nor the interest to correct the code of any SYS file.
That is the task of the driver development team (here: OpenFabrics).
As I stated before, you don't have to correct anything. The deveoplers only have to provide the code, there is no must to comple the code.
It's the spirit of open source to let everyone decide and participate. In the process of compiling code, you can enable certain features,
enable debug or performance optimizations, optimizing the code for different CPUs and architectures),...
So there is no binary "that fits all", as the needs greatly differ.
If you decide to not participate it's perfectly fine, but then don't complain about bad performance or missing features.
Zitat von Fernando im Beitrag #36@Fernando
What do you mean with "build the driver from source"? I will never touch the real driver, which is the *.sys file.
This means, that you should download Visual Studio and other requiered software (like Windows AIK).
Then download the sources of the driver (Visual Studio Project and countless .h and .c files).
Then open the VS project and compile it, which should result in one or more .sys files.
Compiling a piece of software does not requiere code modification, it is just the translation from human readable code to machine executable code.
Programs and libraries are not directly written in binary format. You know, there are programming languages, like C, C++, C#, Java, Rust, Cobol, Pascal, Swift,...
Please, for the love of god, stop using this outdated OS!
Newer hardware is not supported and the OS will not be updated because it is EOL.
Now install Win7/8/8.1/10 and use XP in a virtual machine like VMware Player, Oracle VirtualBox or Microsoft Hyper-V (Hyper-V lacks 3D support).
nVidia advertised some chipsets with integrated graphics directly with the model number of the graphics core.
All information taken from wikipedia:
- nForce 400 / GeForce 6000
- nForce 600 / GeForce 7000
- nForce 700 / GeForce 8000
So the chipset "GeForce 8300" is a MCP78 with GeForce 8300 graphics core.
Zitat von Fernando im Beitrag #403
I totally agree with you.
What we currently not know is, whether a clean install of the "Creator's Update" onto an nForce RAID array will work. I just have compared the content of the scsidev.inf files v10.0.14393.0 (v1607) and v10.0.15063 (v1703). Both are dated 06/21/2006 and their content is identical.
So it seems to me, that problems are foreseeable.
Fernando, ALL Microsoft drivers are dated 06/21/2006 in case a driver update occures the newer driver of the manufacturer is installed.
If Microsoft would push their own driver dates, Windows Update and the driver installer routines would always pick the Microsoft drivers in case of a Windows Update/Upgrade and not the manufacturer ones.
You should compare the SYS and DLL files.https://blogs.msdn.microsoft.com/oldnewt...208-00/?p=95395
You could also try to disable power saving features in your BIOS, like PCIe ASPM or CPU C-states.
Also try adjusting PCIe latency in BIOS. Try different values like 32, 96 or 128. The default should be 64.
I can confirm that the drive is hot-pluggable, but the drive must be connected before the PC is powered on.
If I remove the drive, the drive letter is freed up and the Intel RST console shows the balloon tip "drive removed".
If I plug it pack in, the drive is recognized properly and usable again.
I really don't know why IBM decided to disable the ports during POST.
Dude WTF? I said read the thread!
If I plug in the HDD (with it's own external PSU) before powering on the PC, the drive and port is there (in Intel Rapid Storage Console click on Help and then on System Report).
If I plug it in after the PC is booted to the OS, then the drive is not detected and the port is gone.
The power supply is not the problem!
The port is connected to the chipset (not a fake port)!
Zitat von grml4d im Beitrag #12
you should read your manual ....
your mainboard has a esata3 port
You should read the whole thread. I'm not talking about the ASRock board, I'm talking about an IBM System x3100 M4.
So nobody knows what to do.
FFS, stick to your old GeForce 4 if you desperately want to continue using XP -.-'
The ports are disabled during POST.
If I connect a HDD to the mainboard before powering up the machine the drive is present.
Thanks, but this thread did not offer any additional information.
I already use such cables at home and it works perfectly.
But this IBM system is totally different? Why does the BIOS disable unused ports?
Yes, it is. Reading your previous response I though you meant an eSATA card with its own controller.
I just stated that it is just a pair of cables without a controller.
So why should I contact the manufacturer of the cable?
Now I'm confused...
There is no eSATA adapter. It is just a bracket with eSATA ports that connect to the SATA ports of the Intel AHCI controller embedded in the mainboard chipset.
Somehow the mainboard disables unused ports of the chipset so they are not usable for hotplug drives (although AHCI should be hotplug capable).
I do the very same at home. Maybe it is better to just get an additional eSATA or USB card.
Regarding the wrong BIOS setting: there is only one setting regarding the SATA controller: IDE/AHCI/RAID mode.
Next wekk I'll try a BIOS update: 1.00 (2011) --> 1.40 (2016)
THIS is proper support :D
Please give us more information.
What is the full manufacturer and model of your motherboard?
What is the BIOS version of the motherboard?
I think the SandForce-Controller in the SSD is causing the bad performance.
This drive is listed with 220MB/s write performance.
SandForce-Controllers compress the data to reach good performance.
Your benchmark is set to use incompressible data.
And that's not enough - the SSD has only 52k iops write performance (I have some old Samsung 840 Pro and they have 90k).
In this price segment, even SanDisk would have been a better choice.
TL;DR: cheap drive = bad performance
Forget modding Intel BIOS'. Nobody knows how to do it.
I tried it severeal times with my DQ67SW - no chance!
Intel advertises their security features and this is one of them.
I found the answer some years ago for an older version of Intel RST (I think it was v13)...
I'll find it again.
In the meantime, try this (Post #3).