Search options (Page 72 of 99)

Hi
use the new releases, and report back?

Hi chud
What is the language of your Windows source?

Were you using the latest DriverPacks?
(We should have logs to look at, and I suggest you post them.)

hi

Mass storage INI had double comma errors in the Jmicron [J] section.
I had apparently done a paste of older raw txt from clipboard rather than from the txt I had on screen..
EDIT >> quote from other topic;

Mass Storage DriverPack has therefore been updated to 7.06.1

I found the error and am uploading the fixed file.

Dear Gentlebeings,
a few new driver versions got published and the team members found out these came packed with trouble.
mr_smartepants, Muiz and Bâshrat the Sneaky worked hard to solve the problem with newer Catalyst 7.4 drivers and a few bugs in the driver itself did not make it easy.. Catalyst 7.5 came along, and they could start all over.
But, they finally got the pack together, and a neat feature like widescreen support for notebooks was added.
They included some Nvidia updates as well.
Meanwhile, maxximum, rdsok, and other unfortunate users were victim of a couple other driver updates for chipsets and mass storage.. Lack of support for old hardware in new drivers is a trend, and we chose to keep supporting the old as well.
There was quite a bit of feedback and several methods of fixing it got posted.
The Chipset Driverpack with the fix for Intel's ICH9 was ready quite early in the game, but Intel Matrix Storage drivers stumped us. In the end, I made a U-turn and decided on a change of tactics.
This seems to work, and I take the responsibility if it doesn't.

I can tell you hundreds of hours were spent on fixing the trouble these updated drivers caused, and hope you can appreciate the results.
If you save yourself many hours by using the driverPacks, consider a donation.

I'll link to the overview page.
http://driverpacks.net/DriverPacks/overview.php

Hi
the CD that came with the amilo should be capable of booting it, but in your BIOS the boot-order setting may not be set for booting from the CDrom.

@ helmi or Muiz

the viamach.inf and agp inf were not updated so I guess this might need to be moved to the mass storage section.

Hi

I'm glad to find another guy who can test ICH9

storage706_INTEL_TEST_4

like it says, test for hardware running on intel iastor version 5.5, or 6.2.1002, or 7.5.1017

hi

The problem with changing the mode of the controller (in BIOS) after setup ran its course, is most probably not only in the way "machine.inf" is built, but also a "EMBR" marker.
(in windows 98, driver.cab was built during setup, and migrating a drive to a different type mobo failed most times. XP is even less forgiving.)

The "EMBR" marker has been known to cause trouble as well.

One possible workaround (as long as no formerly array member drive were used), is a setting in BIOS.
ALLOW ESCD refresh, aka NVRAM refresh, aka RESET configuration data.
(with plug and play OS to YES.)
PnP OS YES, will not revert to NO.
BUT, ALLOW ESCD refresh, aka NVRAM refresh, aka RESET configuration data WILL invariably SET ITSELF BACK TO NO after a reboot which refreshed the DMI data in CMOS .
This is stuff I told people several years ago, and kinda used to be a non-issue no more.

However, a BSOD caused by MUP.sys, can be solved by it, as long as it was not a RAID-ARRAY member disk that is used alone.
(in this case, it reports wrong size which you may not notice.. and usually just dissapears once the reboot happens.)

The EMBR problem, would not get solved by clearing CMOS, nor by refreshing ESCD, because it resides on the hard drive itself.
(XP's FIXMBR may cure it. In the old days, FDISK /CMBR and Fdisk /cmbr 2 for fysical drive 2..
And as last resort for persistant entries, a diskmanager doing a soft lowlevel, or a raid chip/Bios doing a real lowlevel (a lowlevel means all data is gone).)

I had hoped somebody with more experience in syprep came along, but above is hands on, just the same.

Hi
D\C\ has chipsets
D\G\ has graphics (the folders in G merge. The exceptions written for a driver have to match the folder.)
D\L has Lan (this one has been screened recently.)
D\M\ has mass storage
D\S has sound, and folders in there also merge (Sound B is quite BIG.)
D\W has wireless (and is HUGE... it will be screened and "weeded" in a nearby future)

Overflow once suggested a way to shorten the path string further by not using \ in nested folders.
If this is done, the exceptions have to be rewritten as well.

chipset706test1