CDROM-Guide forums  

PDA

View Full Version : Registry Edit?


   
jacklanza
Jan 18, 2004, 10:32 PM
I have been trying to update my bios onn my Fic Ad11 mobo. When I d/l the Bios files file and unzip it shows up as aba46 AVG.update, it s/b a bin file. I looked in my registry HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.bin
In the .bin folder are 2 entrys ab (default) reg ze avg.update and
ab (not open) reg ze. Another subfolder is in the above .bin folder Persistenthandler with 098f2470-bae0-11cd-b579-08002b30b-feb.

To make this short, I am unable to flash my bios because this .bin is being changed. I am running Avg antivirus, should I edit the registry and how?

Insomniac
Jan 18, 2004, 10:46 PM
I'd stay away from touching the registry.

Anyway, a bios flash reprograms the bios chip and not the registry.

Firstly, why are you flashing your bios and what do the instructions tell you to do?

Generally, the file is unzipped to a floppy and then the flash is carried out with the floppy in DOS.

ElaineM
Jan 18, 2004, 10:50 PM
I would stop everything, and tell us exactly what the problem was that caused you to want to update the bios in the first place.

jacklanza
Jan 18, 2004, 10:56 PM
Ok, I am getting a constant system error in my event log. Source is acpi. The description is the following: AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0x4d1), which lies in the 0x4d0 - 0x4d1 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance. Then when I go to Microsoft: Details
Product: Windows Operating System
ID: 5
Source: ACPI
Version: 5.2
Symbolic Name: ACPI_ERR_AMLI_ILLEGAL_IO_WRITE_FATAL
Message: %2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Explanation
The system BIOS attempted to incorrectly access hardware resources concurrently with the operating system. This type of access cannot be synchronized and can cause system instability.


User Action
Contact the system vendor for an updated BIOS and follow the vendor's instructions for installation.

Then when I go to Microsoft:
Details
Product: Windows Operating System
ID: 5
Source: ACPI
Version: 5.2
Symbolic Name: ACPI_ERR_AMLI_ILLEGAL_IO_WRITE_FATAL
Message: %2: ACPI BIOS is attempting to write to an illegal IO port address (%3), which lies in the %4 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Explanation
The system BIOS attempted to incorrectly access hardware resources concurrently with the operating system. This type of access cannot be synchronized and can cause system instability.


User Action
Contact the system vendor for an updated BIOS and follow the vendor's instructions for installation.



--------------------------------------------------------------------------------

So, I thought the only way to correct this would be a bios update, any other suggestions would be great!

Insomniac
Jan 18, 2004, 11:07 PM
It will only correct it if that was what the bios flash was designed and released for.

What does the flash say it addresses?

jacklanza
Jan 18, 2004, 11:12 PM
Model AD11
PCB 1.2 / 1.2A (see note)
BIOS Maker AWARD
Version ABA46
Released 2002/1/10
Flash flash802a.exe
Fixes
Fixed shutdown temperature function is failure.
Notes Before you download the BIOS, please check your current revision. For the users who currently use the ABAxx series BIOS, please download ABA46. For the others who currently use the ABBxx series BIOS, please download ABB43. Please make sure you download the correct revision, otherwise you won't be able to boot up your system after flashing the BIOS.

Status release

Any Ideas what I should do?

Btw: Here is the link for the Bios update http://www.fic.com.tw/support/motherboard/doc/procedure.aspx

And I currently am using the aba44 bios, the aba45 corrected a Fixed USB ZIP boot error.

Thankyou all.

Insomniac
Jan 18, 2004, 11:25 PM
It doesn't say anything about fixing your problem, so it won't do much good.

How long have you had this problem?

Have you changed any hardware or bios settings recently?

jacklanza
Jan 18, 2004, 11:38 PM
I really dont know, I have not been using this pc for long, a dvd burner was installed but after the system errors started, according to log its been going on since the beginning of log dec03,03. Also in system log, I get the following error.

DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service ImapiService with arguments "-Service" in order to run the server:
{520CCA63-51A5-11D3-9144-00104BA11C5E}
Then at Microsoft:

Details
Product: Windows Operating System
ID: 10005
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_START_SERVICE_FAILURE
Message: DCOM got error "%%%1" attempting to start the service %2 with arguments "%3" in order to run the server:
%4

Explanation
The Component Object Model (COM) infrastructure could not start the named Windows NT service.


User Action
Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

If the message displays a system, server, or configuration error, contact your service support vendor.

To determine the service vendor

Using Regedit, navigate to the following registry value
HKLM\System\CurrentControlSet\Services\Service Name
The service name is the information displayed in the message.
In the right pane, double-click ImagePath.
The Edit String dialog box is displayed. Leave this dialog box open. If Svchost.exe is displayed in the Value data box, then under the service name, navigate to the Parameters folder and then double-click ServiceDll.
Click Start, and then click My Computer.
Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
Right-click the program name, and then click Properties.
The Properties dialog box for the program is displayed.
To determine who the vendor is for this service, refer to the Version tab.
You can also find the path to the executable file in this tool.



Version: 5.2
Symbolic Name: EVENT_RPCSS_START_SERVICE_FAILURE
Message: DCOM got error "%%%1" attempting to start the service %2 with arguments "%3" in order to run the server:
%4

Explanation
The Component Object Model (COM) infrastructure could not start the named Windows NT service.


User Action
Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

If the message displays a system, server, or configuration error, contact your service support vendor.

To determine the service vendor

Using Regedit, navigate to the following registry value
HKLM\System\CurrentControlSet\Services\Service Name
The service name is the information displayed in the message.
In the right pane, double-click ImagePath.
The Edit String dialog box is displayed. Leave this dialog box open. If Svchost.exe is displayed in the Value data box, then under the service name, navigate to the Parameters folder and then double-click ServiceDll.
Click Start, and then click My Computer.
Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
Right-click the program name, and then click Properties.
The Properties dialog box for the program is displayed.
To determine who the vendor is for this service, refer to the Version tab.
You can also find the path to the executable file in this tool

I have 512mb of 2100ddr ram and running Xp Home.

jacklanza
Jan 19, 2004, 05:32 PM
This topic became very complicated and difficult to correct. That was never my intention. Thanks to all.