Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
38 user(s) are online (26 user(s) are browsing Forums)

Members: 1
Guests: 37

Paul, more...

Headlines

Forum Index


Board index » All Posts (tonyw)




Re: x1000 documentation and other x1000 related questions
Quite a regular
Quite a regular


@kas1e

I know a lot of this has been said before, but...

CFE is old and has not been updated since the original public release. It was modified to recognise FFS as well as
the other FS that it already knew (Ext2, FAT32 etc). It does not recognise or read SFS, NGFS or any other Amiga FS.

At boot time, CFE looks for and reads amigaboot.of (from the device nominated in the ENV-vars command line).
The current version of amigaboot is 54.8, which you should have as a betatester. That amigaboot version can read and boot
any Amiga FS and is the same as amigaboot.ub on the X5000, but is loaded and run by CFE instead of by U-Boot on the X5000.

CFE can certainly load and run amigaboot from a USB stick - that is how I booted my X1000 back when I first got it.
IIRC the instructions were in the PDF manual. The USB stick has to be in the "first" port. Don't remember any more about it,
it was over ten years ago.

You can load amigaboot from a CF card also, but it will probably have to be FAT32. There is no benefit to be gained
by formatting a CF card with FFS. You may be able to write a whole AmigaOS installation onto a CF card, but it would be slow as hell
to run, since it can not do DMA transfers.

Once CFE/U-Boot has loaded and run amigaboot, Amiga file systems FFS, SFS and NGFS are then readable,
on any device that CFE/U-Boot can read.

Amigaboot uses CFE/U-Boot functions to read everything from the boot volume. So you can only boot (load Kickstart modules from)
a device that CFE or U-Boot can read. That means no PCI devices.

AmigaBoot can decode any of the file systems listed above, it only has to be able to read them using CFE/U-Boot functions in raw mode.

cheers
tony
Go to top


Re: AmigaOS4 DOS Tripos Alignment
Quite a regular
Quite a regular


It's moved on in the sense that FileInfoBlocks are obsolescent. We have all spent many happy hours removing such outdated structures from system software and replacing them with calls to IDOS->ExamineObject() etc.

cheers
tony
Go to top


Re: My AmigaOne X5000 twins - I need some help and advice.
Quite a regular
Quite a regular


@Magic

Can you run both X5000s at once? If so, you could connect a serial cable between them and perhaps see (on the /020) what is wrong with the /040.

The X5000 only needs a sniff of electricity. Your graphics card will consume more than the rest of the machine.

Three things to test:

1. Open the machine in a place where you can really get inside it - plenty of light, on the kitchen bench or somewhere.
Remove the screw holding the gfx card and remove the card. With a plastic eraser, run over the PCI-e connector (both sides) lightly. Don't touch the connector with your fingers, but clean off the eraser dust with a small, dry paintbrush.
With the brush, clean the inside of the motherboard connector.
Replace the card and check that the card is not pulled crooked when you tighten the screw. You can bend the bracket slightly to make the screw fit properly.
Repeat for any other PCI-e cards.

2. Check the 3V CR2032 coin cell. Sometimes suppliers leave a small piece of plastic insulator in the socket to prevent the cell from discharging in storage. If you have a voltmeter, check the voltage from the exposed side to chassis - it should be 3.0 to 3.3 V. Less than 3.0 V and it must be replaced (but the X5000 will run with no coin battery in place).

3. Reseat the SATA cable(s). They are notorious for developing bad contact after a time. Make sure that the cable is straight and not pulling the connector to one side - you can bend the cable to make it sit straight.

cheers
tony
Go to top


Re: Strange AllocVec Problem
Quite a regular
Quite a regular


Is that a wombat?

cheers
tony
Go to top


Re: Clock problem on my AmigaOne X5000
Quite a regular
Quite a regular


Hi guys,

Only a few weeks ago we found and fixed a bug in the battclock.resource. It was causing exactly the problem that the OP describes, ie after losing backup power, the clock can't be made to run from battery any more.

"Setclock reset" should re-enable this ability, but due to a bug, it wasn't always working. It affected the X5000/20, X5000/40 and A1222, but some machines worked regardless (for instance my X5000/20 was OK). There are probably some clock chips that behave slightly differently from others.

It has now been fixed (in beta releases at least).

cheers
tony
Go to top


Re: Why call to or any "empty" functions can cause different results of the code in which you insert it?
Quite a regular
Quite a regular


@kas1e

Please try using IExec->DebugPrintF() instead of printf(). "printf()" calls a clib/newlib library function which WILL inevitably cause a Reschedule() and that will allow other tasks to run, even if only briefly.

DebugPrintF() does NOT call any C library code: it writes directly to the serial port without using interrupts, or Waits, or any code that could encourage or force a Reschedule().

My guess is that DebugPrintF() will act the same as (no printf() at all) does, suggesting that your problem is "fixed" by forcing a Reschedule().

If that is true, then you have to find out why preventing a Reschedule() prevents the "compile" from working. I don't know anything about these advanced graphics, so I don't even understand what you are "compiling".
But presumably there is a Process that has to operate on some pseudo-code or tokenised code, and it fails unless something else gets control of the CPU sometimes. Correct?

Go to top


Re: AmiDVD patching
Quite a regular
Quite a regular


I've looked at AmiDVD also, and yes, there is no version string that can be read in the pure binary, but C:Version finds one, so you have to LoadSeg() the binary before it becomes legible.

Perhaps we should LoadSeg() the binary into a buffer, and then try looking at the buffer content.

Has anyone asked Joerg if he is prepared to update the program?

cheers
tony
Go to top


Re: Odyssey 1.23 progress: r5 RC2
Quite a regular
Quite a regular


kas1e,

The binary for Odyssey is huge - some 36 MB. Because it is >32 MB, its PPC FP op-codes can't be translated into SPE op-codes and it will have to run under emulation on the A1222.

Can you split part of the browser off as a library, to keep the largest binary down below 32 MB?

cheers
tony
Go to top


Re: Odyssey 1.23 progress: r5 RC2
Quite a regular
Quite a regular


Sorry if I've missed this in an earlier post.

I downloaded the OS4Depot version and installed it to a fresh partition. I have copied my bookmarks.html file over from the previous installation but I don't see any of my old bookmarks.

Has the format changed? What have I done wrong?

cheers
tony
Go to top


Re: SATA III Port Multiplier on X5000
Quite a regular
Quite a regular


@beanbandit

It won't work on an X5000 or an A1222. It has to be supported by the driver and there is no support for it yet.

cheers
tony
Go to top


Re: Amiga Developer Blog
Quite a regular
Quite a regular


I can understand Matthew's plan: it is to progressively replace the Amiga commands and utilities with new versions that offer the same or better features, but with the advantage that they are free of the Amiga curse.

For that reason, it is preferable (even essential?) to replace the old "tainted" versions with the new "clean" versions, by using the same names. As Matthew has said several times, it is up to us whether we install the new versions over the old, or rename them to something new.

As long as we know the situation, we can avoid a problem when we install Enhancer.

cheers
tony
Go to top


Re: VirusZ & xvs.library is back, but needs help
Quite a regular
Quite a regular


@samo79

Quote:

Thanks for the old and new report, AmigaOS 4.x seems not [to] use MemList in ExecBase any longer as there's unfortunately no list of memory after the ResModules in your report.


The OS4 memory system doesn't work that way any more. You can't just interrogate ExecBase to find out the limits of physical memory (ExecBase is no longer open to the world), and you can't access any part of system memory using physical addresses anyway, since it is all relocated to virtual addresses for each task.

Only the kernel's memory system knows where everything is and it's not telling - you don't need to know.

You could probably get the size information from U-Boot before AmigaOS is booted, but once the system is running, you won't find memory at those addresses and your task will just crash.

cheers
tony
Go to top


Re: AmiDVD doesn't recognize the drive
Quite a regular
Quite a regular


@Paul

AmiDVD does not work on the X5000 or the A1222. It has a list of "legal" platforms and the last "legal" one was the X1000.

cheers
tony
Go to top


Re: Sgrab
Quite a regular
Quite a regular


@Thematic

There are no sources for SGrab in the Hyperion repository, so we can't "fix" it. However, I use it frequently without a problem.

Can you describe a sure-fire means of provoking a crash/lockup?

cheers
tony
Go to top


Re: Getting X5000. . . this graphics card work?... or this one?
Quite a regular
Quite a regular


@Paul

Long time no hear, hope you and your family are well.

You know whom to call if you have problems.


cheers
tony
Go to top


Re: Multiple Monitors and screen orientation
Quite a regular
Quite a regular


@Ami603

Thanks. Now I just need to find one. My local DIY shop is advertising them at AU$700, not in stock. Another on-line place says they are "Discontinued".

cheers
tony
Go to top


Re: Multiple Monitors and screen orientation
Quite a regular
Quite a regular


@Ami603

What refresh rate can you run on your two screens?

I see from the Matrox site that running three screens slows you down to 50 Hz, but doesn't say anything about just two.


cheers
tony
Go to top


Re: How to allocate TimeRequest
Quite a regular
Quite a regular


@billyfish

The code on the wiki site looks OK to me. Are you sure you copied it all and didn't leave out some stuff?

Especially the need to create your own MsgPort before you call AllocSysObject() ?


cheers
tony
Go to top


Re: password hacked?
Quite a regular
Quite a regular


@xenic

I'va also received blackmail emails over the last couple of days, just as I did some years ago - same old aw.net password that I changed many years ago now.

I wouldn't worry about it.

cheers
tony
Go to top


Re: Possible WritePixelArray bug - OS4.1
Quite a regular
Quite a regular


@flash

I think you are a little confused by the terms involved.

CLUT is a lookup table where each pixel's colour is indexed by an 8-bit byte in the bitmap. You can only have 256 different colours at once, although you can choose and change your 256 colours at any time.

The lookup table contains RGB values for each of the 256 colours. Depending on the graphics mode, the RGB values can be any colour resolution (number of bits per colour). Usually 24 or 32 bits per colour are used, but it can be 8, 15, 16 bits depending on the mode (not sure about that).

The bitmap, however, contains only the 8-bit bytes describing the colour number for each pixel; thus it contains only 8-bit data.

cheers
tony
Go to top



TopTop
(1) 2 3 4 ... 34 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project