Welcome, Guest. Please login or register.
Forums
« previous next »
Pages: [1]   Go Down

Author Topic: AsyncWB delete error OS3.9  (Read 2336 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline MilooTopic starter

  • Full Member
  • ***
  • Join Date: Mar 2007
  • Posts: 165
    • Show only replies by Miloo
AsyncWB delete error OS3.9
« on: March 29, 2009, 09:53:31 AM »
Just reinstalled OS3.9 but when I go to copy/move/delete a guru comes up with :


AyncWB - delete process Program failed (error #8000003d). Wait for disk activity to finish.

Why is it doing this?
Logged
A1200/68882/AMD Slot A 1Ghz in EZPC case, Blizzard 060@66Mhz/SCSI IV, PortJnr, 194Mb fast ram, 4Gb CF HD, OS 3.9, Indivision AGA
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #1 on: August 19, 2009, 06:25:44 AM »
I know it's a bit late, but I just installed 3.9 and I had the same problem.
Installing a newer version of Asyncio.library solved it.
You can find the newer 68k version in the asyncio-ppc archive on aminet.
Logged
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #2 on: August 19, 2009, 08:13:42 AM »
Hmmm, thought it was solved, but the problem is back.
I ended up removing asyncwb from wbstartup.
 
Also the BB2 romupdate made my a1200 quite unstable, so I don't use it.
Logged
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #3 on: August 20, 2009, 08:26:15 PM »
I can use AsyncWB again.
 
I have a Microbotics 1230XA accellerator and I use the "CPU fastrom" command to remap the kickstart rom in fastram.
This worked like a charm under WB3.1, but it caused trouble under 3.9.
My system was horribly unstable. Gurus all over the place.
I removed the CPU command from ss and my system is pretty stable now.
 
Still have some trouble with the BB2 romupdate though. Had to skip exec.library, but there are other updates in it that also cause trouble.
For now I just disabled the romupdate.
Logged
 

Offline AmigaMance

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 1278
    • Show only replies by AmigaMance
Re: AsyncWB delete error OS3.9
« Reply #4 on: August 21, 2009, 01:18:36 AM »
AsyncWB is a nice commodity but it has many bugs. I have made at least one post in the past in where i list some of them. Workench.library is partly responsible for this, so if you install the updated version from here:
http://aminet.net/package/util/sys/OS39_update_patches
http://aminet.net/package/util/sys/OS39_update_patches2
AsyncWB will behave a little nicer, but it will still give problems and that's why i'm not using it.

As for the exec.library of AOS 3.9, it's actually more stable (but slower) than the 3.1's one. The thing is that it's more picky with badly coded programs. Therefore, i think that you should try to locate these programs and replace them with better ones.
 Btw, in some accelerators the exec.library of AOS 3,1 is loaded in the chip-ram and this causes a big performance penalty. You can check this from SysInfo or other system monitors.

 About the stability problems that you experience, i recommend to install the mcpramlibpatch command from the MCP archive on Aminet, after setpatch.
« Last Edit: August 21, 2009, 01:20:37 AM by AmigaMance »
Logged
A1200 PPC user.
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #5 on: August 21, 2009, 03:47:18 AM »
Quote from: AmigaMance;520325

About the stability problems that you experience, i recommend to install the mcpramlibpatch command from the MCP archive on Aminet, after setpatch.

I already use mcpramlibpatch.
 
In my case the kickstart remapping  with the "CPU fastrom" command really was the culprit. I haven't had a single guru since removing it from my startup-sequence.
 
I can't use blizkick with my accellerator, so I guess no kickstart remapping for me.
Logged
 

Offline Damion

Re: AsyncWB delete error OS3.9
« Reply #6 on: August 21, 2009, 07:06:19 AM »
Have you given MuFastRom a try?
Logged
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #7 on: August 21, 2009, 12:25:33 PM »
Quote from: Damion;520364
Have you given MuFastRom a try?

Thanks for the tip Damion.
 
I've just tried it. According to sysinfo, when using mufastrom, the speed of my CF card really goes down :angry:
 
I think for now I just won't use a kickstart remapper tool.
 
As for the romupdate, I think it's the console.device update that's giving me headaches. Have to investigate this a little further.
Logged
 

Offline MozzerFan

  • Hero Member
  • *****
  • Join Date: Mar 2005
  • Posts: 607
  • Country: 00
    • Show only replies by MozzerFan
Re: AsyncWB delete error OS3.9
« Reply #8 on: August 23, 2009, 03:17:12 PM »
Just had a better look at mufastrom. It doesn't seem to take down my CF speed as seriously as I first thought.
The speed of my CF card is a little slower, but overall system speed is a little faster.
 
HOWEVER, the gurus still happen when I use mufastrom.
 
So, both with cpu fastrom and mufastrom I get gurus. All the same guru : 8000000b line 1111 emulator error.
This even happens with normal copy/delete operations.
If I don't use a kickstart remapper tool all is fine.
 
Under WB3.1 it also doesn't happen. Just checked my 3.1 guruhistory.dat file.
Didn't have a guru in the past month. That is until I installed os3.9.
 
I don't want to go back to 3.1, so I just won't use a kickstart remapper.
« Last Edit: August 23, 2009, 06:30:57 PM by MozzerFan »
Logged
 
Pages: [1]   Go Up
« previous next »