Jump to content

Intel infinst_autol.exe did solve the problem until 2006


pinecloud

Recommended Posts

:unsure:Intel infinst_autol.exe did solve the problem until 2006

When you try to install newer chipset.inf file today i.e., “infinst_autol.exe or intelata_enu.exe”, they refuse with “Operating System not supported” or even “rundll32 export failure” messages. If you carefully extract the file content to many of *.cat file level and examine them carefully. I see the $chicago$ headers and ‘donothing’ instructions within them. I am not even a coder but just a photographer and graphic artist, I can still see that Intel was influenced by somebody in the background. Perhaps one of software giants stopped Intel’s driver development team from releasing drivers suspected detrimental to the sales of new software campaign. The time and motivations seem to co-incide with discontinuation of innovative and altruistic Winternals projects from Texas. The Winternals was well capable of providing add-on component pack for Windows NT and Windows 9X at $29 (meaning such pack can appear on eBay for $4.99 range p&p inclusive) per seat to perform the today’s role of Windows XP platform (application compatibility wise) aside from ADS (alternative data stream) which I do not care for in any means. Games of software giants play are not as devastating as oil price schemes detrimental to the future economy of our country but it’s really something. Question of morale of the country strived on philosophy of freedom.

Pinecloud

Economic interest was not build into hardware enumeration hierarchy until 486 or even early P5. Pci/ven code started to appear in Windows registry after P5 era. Windows block device mapping has no logical relation to physical device mapping e.g., c0t0d0p0s:b (hba ID, target ID, disk ID, partition ID, slice ID) which makes more sense over Windows device vendor signature based mapping perhaps arising from its economic interests. Playing with pci/ven codes cut and paste using established models already running on Windows 9X and XP as reference guide at “Brute Force Locksmith Method” eventually works because it has worked on setting up PCI-E video card. for me. Doing it on disk enumeration has much more threat of losing data. That is why I have not tried as hard.

Link to comment
Share on other sites


This form already has improved generic ATA drivers.

Generic SATA drivers are coming soon, thanks to the efforts of Xeno in porting their NT counterparts to 9x.

Contrary to intuition, generic drivers are usually better than vendor specific ones, probably because they are desired by a vaster audience, causing greater motivation for development, and have a far wider testing audience.

That, and focusing on standard compliance in hardware use is not that different from applying standard compliance in code paradigms, which commonly adds stability. In other words, "less hackity-hack-hack".

That being said, you are somewhat exaggerating in your claims that Intel may have been influenced to discontinue their drivers. Intel where always behind on drivers, even before certain OSs reached EOL. They hardly ever release any worthwhile drivers for any OS, and the ones they do release are usually buggy as hell.

If you ever had the misfortune of coming to use Intel hardware, I got one tip for you: Third party drivers. Would have given the exact same tip 8 years ago, too.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...