LHA depacking gone awry

Amiga1992 · 27 June 2008, 04:20

I've had this problem since I got my Amiga, but I always thought it was one of the patches doing it because when I booted from my other partition, up until yesterday, the problem would go away.

But now it happens every time.

I cannot depack any LHA file. The software randomly (at different files in the process, it's not always at the same point) says there has been a CRC or I/O error and then "**skipping extraneous/corrupt data"

The files are NOT corrupted because I can extract them in my emulator 100% fine (tested both E-UAE and WinUAE)

Could this be a memory problem? I am afraid the memory in my accelerator has gone bad or something.

This is also no device problem, I tried depacking from the internal CF, from the Memorystick on the PCMCIA, and even from RAM: same results.

Config is: A1200 with A1230XA, 030@50Mhz, 32MB Fast RAM
Internal CF with 3.0 installed.
Kickstart 3.0

Do you think this could be a problem of the power supply?

Any help would be greatly apreciated.

Amiga1992 · 27 June 2008, 04:40

Again answering myself with another one.

This one might help other users of Microbotics MA1230XA

Seems like the corruption issues are created by the AUTOXA software.

AUTOXA loads the Fastram memory of the card into the system (yeah it's shit that it's not autoconfig).
Everything runs fine except when you try to load the software again. Something wrong happens and this problem starts.

I am no hardware guru but I'd love to have someone fix this, maybe releasing an updated AutoXA software.

For now my solution is making an "echo" in my startup that asks if i wanna load the autoxa software. The funny thing is, autoxa realizes it's active already if you load it twice, but it apparently is doing something that creates trouble. The obvious fault for me is in LHA, but this problem might be affecting other softwares.

Anybody up to take a look? or tell me what I should look for in SnoopDOS?

Amiga1992 · 27 June 2008, 05:39

Here I am talking to myself again :P

Upon further inspection, this is what it seems to happen.

You load the AutoXA soft. Loads fastram into system.
This thing is resident so it keeps the fastram there even after you reset.

Here is the problem. Once you reset, the memory is there, but THIS PROBLEM SURFACES. I don't know where the conflict is or what (never used Snoopdos, will try it later), but for the software to work fine, you have to REMOVE it from the system before resetting. Also, when you execute it after the reboot, load it first thing with the NOREBOOT parameter.

This is a big pain in the ass. I don't know, as I said, which other apps it might affect, but LHA is annoying enough.

It's too late now so after some sleep and waking up, I will inspect the thing with Snoopdos.

rkauer · 27 June 2008, 06:30

Quote:

Originally Posted by Akira

Here I am talking to myself again :P

Upon further inspection, this is what it seems to happen.

You load the AutoXA soft. Loads fastram into system.
This thing is resident so it keeps the fastram there even after you reset.

Here is the problem. Once you reset, the memory is there, but THIS PROBLEM SURFACES. I don't know where the conflict is or what (never used Snoopdos, will try it later), but for the software to work fine, you have to REMOVE it from the system before resetting. Also, when you execute it after the reboot, load it first thing with the NOREBOOT parameter.

This is a big pain in the ass. I don't know, as I said, which other apps it might affect, but LHA is annoying enough.

It's too late now so after some sleep and waking up, I will inspect the thing with Snoopdos.

Akira, I have this accelerator too.

Under ks3.1 it don't need the AutoXA software to add the RAM to system.
All you need is run the setXA once to program the accelerator's settings (CPU and FPU speed, RAM clock & wait states, other), save to its flash RAM and nothing more.

If you want to move the ROM contents to fast RAM, just add this line in your s-s (must be the very first line):

"C:CPU fastrom"

Problem solved!

BTW: anyone know how Zetr0 send me his flu? I'm still puzzled.

Amiga1992 · 27 June 2008, 07:03

I think there is an energy problem.
NOTHING works now.
I am puzzled.
Maybe the memory chips went wrng
maybe its this shit old PSU with little juice

whatever it is, it ipsses me off.

anything that gets loaded to RAM corrupts the memory
let me try setXA and report back, thanks for that tip

Amiga1992 · 27 June 2008, 07:25

I am thinking that maybe my memory is defect.
Also, I have KS 3.0, so SetXA wont let me autoload the memory I believe

I used the MBRTest, here's results:

|========================================================================|
| MBRTest-2 is a product of MicroBotics, Inc. |
| 1251 American Parkway, Richardson, Texas 75081, USA - (214)437-5330 |
| Manufacturers of Great Peripheral Products Since the Amiga Was Born! |
|========================================================================|

Selected tests:
MSCAN MARCH DTADD FLOAT
Selected memory area:
FAST RAM at address 8000000, size 2000000, 32bit
Cycle 1, MSCAN, FAST RAM at 8000000 started
Cycle 1, MSCAN, FAST RAM at 8000000 done in 00:00:29
Cycle 1, MARCH, FAST RAM at 8000000 started
--> MARCH error 1 at 82008f0 (2008f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 2 at 82010f0 (2010f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 3 at 82028f0 (2028f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 4 at 82030f0 (2030f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 5 at 82048f0 (2048f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 6 at 82088f0 (2088f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 7 at 820c8f0 (20c8f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 8 at 8a008f0 (a008f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 9 at 8a010f0 (a010f0), wrote 55555555, read 45555555
--> lines: 28.
--> MARCH error 10 at 8a050f0 (a050f0), wrote 55555555, read 45555555
--> lines: 28.
Cycle 1, MARCH, FAST RAM at 8000000 done in 00:00:30
Cycle 1, DTADD, FAST RAM at 8000000 started
Cycle 1, DTADD, FAST RAM at 8000000 done in 00:00:23
Cycle 1, FLOAT, FAST RAM at 8000000 started

Now, what the hell is the MARCH test and what is failing there? Is my memory module defect?

Amiga1992 · 27 June 2008, 08:04

I will not use my Amiga until I get a proper PSU.
I think it might have something to do with this.
I mean, this problem occurred before, but not all the time and stuff would run, now nothing works.

I changed the memory speed to 60ns (it was 70) since I found some data on the web that might hint at that being the correct speed. But I don't want to risk my system any way.

I might order some memory modules as well just in case

chiark · 27 June 2008, 09:33

Blimey, I thought I had bad luck with Amigas sometimes: chin up, it can only get better.

Running 60ns memory at 70ns will not cause any problems, but running 70ns memory at 60 can do.

The output is telling you you've fundamentally got a problem reading and writing memory - either some duff memory or duff connection.

Remove, clean connectors and SIMM, reseat, try again. If you get the same, look suspiciously at the memory and every connection in the system

A march test is, as I understand it, a test that writes and reads memory to march the memory through its paces. It can be simple or complex, but it's a full shakedown for the memory...

Amiga1992 · 27 June 2008, 09:52

It passes the MARCH test when i have just cold started the machine, but as soon as I use the memory, I get that error.

I have taken the module out and put it back again. Still no dice.
But the funny thing is i always had this prob, so I guess I bought it with a bad memory module?

I'll try with new ones.

chiark · 27 June 2008, 10:33

That is weird. Very, very weird... Could be a component warming up and failing, but that's... strange.

Have you got another stick of ram you can use, or any way of testing the RAM you're using (memtest86 in an old PC)?

chiark · 27 June 2008, 10:40

Actually, the more I think about this, the more it sounds like it could be a power problem: random stuff happening, etc. With the stuff you've got, you're probably right on the limit of your PSU.

Amiga1992 · 27 June 2008, 17:11

Well I will buy a picoPSU and make the mod ASAP to debunk the power problem. Until then, I will not power up the Amiga in fear something might fuck up.

Just in case, I am scouring the web for new memory modules as well. They're pretty cheap anyway.

chiark · 27 June 2008, 18:06

Yeah, you should get one for pennies (literally) from ebay. Good luck!

rkauer · 27 June 2008, 21:49

Quote:

Originally Posted by chiark

Yeah, you should get one for pennies (literally) from ebay. Good luck!

Effy have some 128Mb/60ns SIMM to sell. Ask him! Works flawlessly on mine MBX (just set the memory at 70ns).

He is reachable on Amibay or A.org.

BTW: check the caps on the motherboard. Old SMD caps are prone to fail without notice, causing a bunch of nasty behaviour on A600/1200/4000.

BTW: the original 1200 PSU is a no-go with even a humbly expanded Amiga. And the MBX is not exactly "meagre" in power requirements. Better hack an AT/ATX or pico-PSU (even a 60W unit is enough, remember to add more "juice" to the +12V PSU).

rkauer · 27 June 2008, 21:51

Oh, for nasty behaviour I mean it crashes while running. The Miggy don't do a strip-tease for you. Lost the hopes!

A3000T · 25 March 2022, 19:26

Any out there My MBRTest-2 disk went bad and I need the files to get my program working
I have the main program but need the support files on disk. Please send them to a3000t@yahoo.com
Thanks

jotd · 26 March 2022, 12:49

Microbotics MA1230XA is an inferior piece of trash compared to the blizzard boards.

27 June 2008, 04:20	#1
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	LHA depacking gone awry I've had this problem since I got my Amiga, but I always thought it was one of the patches doing it because when I booted from my other partition, up until yesterday, the problem would go away. But now it happens every time. I cannot depack any LHA file. The software randomly (at different files in the process, it's not always at the same point) says there has been a CRC or I/O error and then "*skipping extraneous/corrupt data" The files are NOT corrupted because I can extract them in my emulator 100% fine (tested both E-UAE and WinUAE) Could this be a memory problem? I am afraid the memory in my accelerator has gone bad or something. This is also no device problem, I tried depacking from the internal CF, from the Memorystick on the PCMCIA, and even from RAM: same results. Config is: A1200 with A1230XA, 030@50Mhz, 32MB Fast RAM Internal CF with 3.0 installed. Kickstart 3.0 Do you think this could be a problem of the power supply? Any help would be greatly apreciated. Last edited by Amiga1992; 27 June 2008 at 07:28.*

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Seeking platform independant Crunchmania 'CrM2' data file depacking	ubyte	Coders. General	21	06 November 2009 19:48
I know nothing about LHA...	Muzkat	New to Emulation or Amiga scene	11	19 July 2006 00:53
Lha	swirligig	New to Emulation or Amiga scene	5	25 June 2002 01:32
Lha!	Pixel	New to Emulation or Amiga scene	8	31 May 2002 19:05
Lha??	Lisa	New to Emulation or Amiga scene	2	04 May 2002 13:47

27 June 2008, 04:40	#2
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	Again answering myself with another one. This one might help other users of Microbotics MA1230XA Seems like the corruption issues are created by the AUTOXA software. AUTOXA loads the Fastram memory of the card into the system (yeah it's shit that it's not autoconfig). Everything runs fine except when you try to load the software again. Something wrong happens and this problem starts. I am no hardware guru but I'd love to have someone fix this, maybe releasing an updated AutoXA software. For now my solution is making an "echo" in my startup that asks if i wanna load the autoxa software. The funny thing is, autoxa realizes it's active already if you load it twice, but it apparently is doing something that creates trouble. The obvious fault for me is in LHA, but this problem might be affecting other softwares. Anybody up to take a look? or tell me what I should look for in SnoopDOS?

27 June 2008, 05:39	#3
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	Here I am talking to myself again :P Upon further inspection, this is what it seems to happen. You load the AutoXA soft. Loads fastram into system. This thing is resident so it keeps the fastram there even after you reset. Here is the problem. Once you reset, the memory is there, but THIS PROBLEM SURFACES. I don't know where the conflict is or what (never used Snoopdos, will try it later), but for the software to work fine, you have to REMOVE it from the system before resetting. Also, when you execute it after the reboot, load it first thing with the NOREBOOT parameter. This is a big pain in the ass. I don't know, as I said, which other apps it might affect, but LHA is annoying enough. It's too late now so after some sleep and waking up, I will inspect the thing with Snoopdos.

27 June 2008, 07:03	#5
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	I think there is an energy problem. NOTHING works now. I am puzzled. Maybe the memory chips went wrng maybe its this shit old PSU with little juice whatever it is, it ipsses me off. anything that gets loaded to RAM corrupts the memory let me try setXA and report back, thanks for that tip

27 June 2008, 07:25	#6
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	I am thinking that maybe my memory is defect. Also, I have KS 3.0, so SetXA wont let me autoload the memory I believe I used the MBRTest, here's results: \|========================================================================\| \| MBRTest-2 is a product of MicroBotics, Inc. \| \| 1251 American Parkway, Richardson, Texas 75081, USA - (214)437-5330 \| \| Manufacturers of Great Peripheral Products Since the Amiga Was Born! \| \|========================================================================\| Selected tests: MSCAN MARCH DTADD FLOAT Selected memory area: FAST RAM at address 8000000, size 2000000, 32bit Cycle 1, MSCAN, FAST RAM at 8000000 started Cycle 1, MSCAN, FAST RAM at 8000000 done in 00:00:29 Cycle 1, MARCH, FAST RAM at 8000000 started --> MARCH error 1 at 82008f0 (2008f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 2 at 82010f0 (2010f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 3 at 82028f0 (2028f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 4 at 82030f0 (2030f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 5 at 82048f0 (2048f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 6 at 82088f0 (2088f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 7 at 820c8f0 (20c8f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 8 at 8a008f0 (a008f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 9 at 8a010f0 (a010f0), wrote 55555555, read 45555555 --> lines: 28. --> MARCH error 10 at 8a050f0 (a050f0), wrote 55555555, read 45555555 --> lines: 28. Cycle 1, MARCH, FAST RAM at 8000000 done in 00:00:30 Cycle 1, DTADD, FAST RAM at 8000000 started Cycle 1, DTADD, FAST RAM at 8000000 done in 00:00:23 Cycle 1, FLOAT, FAST RAM at 8000000 started Now, what the hell is the MARCH test and what is failing there? Is my memory module defect?

27 June 2008, 08:04	#7
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	I will not use my Amiga until I get a proper PSU. I think it might have something to do with this. I mean, this problem occurred before, but not all the time and stuff would run, now nothing works. I changed the memory speed to 60ns (it was 70) since I found some data on the web that might hint at that being the correct speed. But I don't want to risk my system any way. I might order some memory modules as well just in case

27 June 2008, 09:33	#8
chiark Needs a life Join Date: Jan 2008 Location: England Posts: 1,707	Blimey, I thought I had bad luck with Amigas sometimes: chin up, it can only get better. Running 60ns memory at 70ns will not cause any problems, but running 70ns memory at 60 can do. The output is telling you you've fundamentally got a problem reading and writing memory - either some duff memory or duff connection. Remove, clean connectors and SIMM, reseat, try again. If you get the same, look suspiciously at the memory and every connection in the system A march test is, as I understand it, a test that writes and reads memory to march the memory through its paces. It can be simple or complex, but it's a full shakedown for the memory...

27 June 2008, 09:52	#9
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	It passes the MARCH test when i have just cold started the machine, but as soon as I use the memory, I get that error. I have taken the module out and put it back again. Still no dice. But the funny thing is i always had this prob, so I guess I bought it with a bad memory module? I'll try with new ones.

27 June 2008, 10:33	#10
chiark Needs a life Join Date: Jan 2008 Location: England Posts: 1,707	That is weird. Very, very weird... Could be a component warming up and failing, but that's... strange. Have you got another stick of ram you can use, or any way of testing the RAM you're using (memtest86 in an old PC)?

27 June 2008, 10:40	#11
chiark Needs a life Join Date: Jan 2008 Location: England Posts: 1,707	Actually, the more I think about this, the more it sounds like it could be a power problem: random stuff happening, etc. With the stuff you've got, you're probably right on the limit of your PSU.

27 June 2008, 17:11	#12
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,665	Well I will buy a picoPSU and make the mod ASAP to debunk the power problem. Until then, I will not power up the Amiga in fear something might fuck up. Just in case, I am scouring the web for new memory modules as well. They're pretty cheap anyway.

27 June 2008, 18:06	#13
chiark Needs a life Join Date: Jan 2008 Location: England Posts: 1,707	Yeah, you should get one for pennies (literally) from ebay. Good luck!

27 June 2008, 21:51	#15
rkauer I hate potatos and shirts Join Date: Oct 2007 Location: Sao Leopoldo / Brazil Age: 58 Posts: 3,482	Oh, for nasty behaviour I mean it crashes while running. The Miggy don't do a strip-tease for you. Lost the hopes!

25 March 2022, 19:26	#16
A3000T Registered User Join Date: Feb 2022 Location: Chubbuck, Idaho USA Posts: 19	Any out there My MBRTest-2 disk went bad and I need the files to get my program working I have the main program but need the support files on disk. Please send them to a3000t@yahoo.com Thanks

26 March 2022, 12:49	#17
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,411	Microbotics MA1230XA is an inferior piece of trash compared to the blizzard boards.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)