Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
113 user(s) are online (80 user(s) are browsing Forums)

Members: 0
Guests: 113

more...

Headlines

Forum Index


Board index » All Posts (Hypex)




Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
Just in case someone in this topic found it intersting, i created some big video about x1000 on which i spend for about a week.


I thought the video was big because the X1000 was slow to boot.

That was quite extensive. Interesting footage there. Remember when computing was fun and Trevor had brown hair?

I couldn't imagine hacking into a case with a grinder. Even a cheap one. I have issues with modifying new products.

I noticed you booted the OS4 manually. Was the CD boot menu broken? With standard HD and CD setup even HD boot should find CD first and boot it.

I didn't see USB booting so the mystery still remains. Now you can see why a patched CD booter was needed. Especially with an R7 250. One thing though, with the RadeonHD v5 driver, you have no soft reboot support. So if you want to reboot, even just reboot AmigaOS, you will be unable too and will need to wait for a full slow boot again.

Go to top


Re: Amiga dos script help
Just popping in
Just popping in


@Raziel

I may have spoken too soon. Just tested and only get errors. It may not exist in our ARexx so you may need the "lineup kludge" after all.

Go to top


Re: Amiga dos script help
Just popping in
Just popping in


@Raziel

I found the answer last night bur forgot to post it. So SAY always adds a newline and cannot be changed. But, this is an old problem and I found the answer. The answer is CHAROUT which will print characters without a newline.

Somewhat quirky as it needs a comma like this:
CHAROUT ,'String"

https://groups.google.com/g/comp.os.os ... rammer.misc/c/U3cSXUFAWE4

Go to top


Re: Amiga dos script help
Just popping in
Just popping in


@Raziel

What are you using to print your output? If you are using Echo you can use the NOLINE switch.

https://wiki.amigaos.net/wiki/AmigaOS_ ... OS_Command_Reference#ECHO

Go to top


Re: Amiwest 2022. Any OS4 announcements expected?
Just popping in
Just popping in


@benny

Quote:
There should be a public demo of ExecMP at the A-Eon booth, according to a slide.


Is ExecMP the secret name of of the kernel now revealed? Exec Multi-Processing? I tried to look up this ExecMP and got nothing back. So it must still be a secret nobody is talking about yet on the forums. The only thing I found is a secret report from the CIA about the cost of an Amiga being a secret.


https://fas.org/blogs/secrecy/2014/09/amiga-cost/

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@TearsOfMe

Quote:
But i get in trouble when i broke this port. Get me a pain of headache before i came to the solution to boot from a CFCard Adapter in the old atapi port on the mainboard.


I take it this was easier than needing to backup, reformat and restore the HDD? Assuming you didn't have space for a small boot partition.

USB stick could possibly be used but may have needed a hub to share with keyboard and plugged in keyboard port. But it's not an internal solution.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
The problem with USB boot, is that it can't boot when it ISO (so rawritten from x1000_iso image). I.e. you type "boot -fs=iso usbdisk0:amigaboot.of" it finds just fine, loads up, but then, amigaboot.of know a shit about "fs=ISO" , it's know about FFS, SFS, NGFS and stuff.


Technically amigaboot.of knows about ISO because it can boot off a CD! An O4 install CD isn't fancy like an OSX install CD with HFS. An OS4 install CD is just standard ISO9660 with RockRidge extensions. And amigaboot needs to scan for it when it boots off CD drive. so it can certainly do it. If it doesn't find it then it's not looking in the right place or isn't scanning usb. It should know the boot source but I don't know if it does.

Also, the "-fs-iso" tells only CFE what filesystem it is, so CFE can easily load from USB. But after CFE loads amigaboot.of CFE can do no more, it's out of its hands. In fact, at that point, CFE is effectively dead when amigaboot loads as a binary load will destroy CFE and it will crash if the binary exits.

Quote:
IMHO boot from USB it possible fully (not just amigaboog.of), but for that, you should format your usb stick as FFS, and put all the files on it (and also make it bootable too). Then amigaboot.of probabaly can find filesystem is know, and then boot from it.


I tried all that, FFS. SFS, then gave up. It's like kicking a dead horse. If amigaboot.of won't read USB, purposely or otherwise, then it simply won't boot from it.

I think that 2015 one you found with specific USB support is the go. Or it's writing your own boot loader. Which is beyond the scope of the average user and simply booting from USB shouldn't be that hard!

Quote:
I do not know through how done on x5000 that boot from rawwritten iso on usb stick works, maybe they do change UBoot to know something else in compare with CFE.


They probably geared it towards the needs of the modern market. I can get Linux to boot off USB from UBoot on my XE. But when I created an autoboot USB image I had to write a stub bootlock and modify ub2lb to check USB. So my stub was RDB boot block like SLB that fit on start of ISO image so UBoot would find it. It was just a chain loader I called UBL (Universal Boot Loader) that then checked for an ISO bootblock and executed it. So the end result was ub2lb being loaded. I had to slightly modify that to be USB aware. I'd pretty much defined my own XE ISO/Hybrid standard. The image could be written to CD or USB. And boot off both. In fact, with some editing of the UBoot boot command, it could also auto boot off USB if it was left in drive on boot up.

In the case of CFE, aside from CFE bugs not able to detect and mount USB drives, CFE can load or boot from USB. The obvious problem here is amigaboof.of. Which for some reason isn't scanning USB devices.

It's supposed to share common code with amigaboot.ub, which can boo from USB, but how much? Both would need some kind of HAL, or FAL, Firmware Abstraction Layer, since one is using an OpenFirmware API and the other a UBoot API. Whatever it is doing it isn't scanning USB drives or actually mounted drives. I don't know how much is forged in the OF tree from CFE, but something is missing.

Go to top


Re: AmiDVD patching
Just popping in
Just popping in


Need to check versions but AmiDVD from Enhancer 1.5 was working fine with Update 2 here.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
Yeah, x5000 one looks like old classic menu, while X1000 imho looks more "NG". Dunno, x1000 one looks imho better. On x1000 this menu also placed over the main x1000 image, which make better visual look as well and it also fully customizable , i do not know if on X5000 i can customize those entries at all in the menu: probabaly they just hardcoded, and you only can change actual commands which will be executed when you choose what you need in menu, but not the menu itself.


Okay I see what you mean. That's a real customised menu. I got as far as one for AmigaOS and two for Linux.

Since I find it easier to manage menus in software, even though it's not as pretty, my main boot menu looks like this. I don't have a HDMI capturer. So this is a recreation.

Resized Image


Quote:
On x1000 it's just done logicaly imho. You just power on machine and have menu, have words "hit this key to enter to firmware" or choose what you need , or let it boot on defaults. All good.


It of course has to be set up from hand with the quirky CFE CLI as it has no built in editor.

Quote:
But on x5000, as it now, you should know that you need to hit "esc" to enter to firmware, but then you didn't enter to firmware, you inter to the "early startup menu", and only from this one you can enter to firmware, which btw, called "command line" instead (dunno why).


I find Esc easier to remember. Top left go. Where as with F key I had to scrounge around looking for it and have missed it. Especially after changing timer to 1 second! Most annoying is laptop with F2 or some illogical key that's hard to remember.

So I tested again on USB. Made up a small boot image with FE files and amigaboot.of. Using AmiDVD and set to bootable. Was able to load the bootloader from USB. But amigaboot did not list the USB as a boot source. So it doesn't work. If USB support was added in 2015 then it must be buggy or they removed it. I'd say we'd need to track down that version. Or do what they did with ub2lb to boot Linux, write your own USB booter!

After re-reading it I think what Tony is referring too is just loading amigaboot.of from USB. That works. Actually booting OS4 off USB presently does not.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@tonyw

Quote:
The USB stick has to be in the "first" port. Don't remember any more about it, it was over ten years ago.


Is that the first port on back panel or first port on front case? I suspect now it's first port on back as in keyboard port. This would explain why it won't mount from my front ports but will mount in my keyboard hub.

Quote:
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


Well, there's one benefit, FFS is more robust. FAT32 is just too buggy in CFE. Well, CFE isn't very robust perhaps. You can write to FFS and CFE will see it. But write to FAT32 and it will go missing in CFE. I suspect this is because OS4 did not dismount the FAT32 disk so it is in a manner of speaking invalidated. It needs to copy whatever Windows is doing as you can pull it out now without ejecting which is like the Amiga way.

FAT32 can corrupt easily. My phone suddenly crashed and rebooted. It would not mount the FAT32 SD card. Did not have any basic tools to check or clear file system. Only format. Didn't know FAT support was so bad in phones.

FAT16 is better somehow. CFE likes it better. Ext2 another option. Not sure of transparent OS4 support with FUSE. So FFS remains best from CF card I would say from my USB experience.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
What is strange is why X1000 installation CD didn't ask me about bootloader .. because i am sure, when i install OS4FE on pegasos2, it surely did ask me to where place bootloader (and there i the same have "Boot" volume).


They must have lapsed and forgot to include this boot breaking step in the installer as it seems no one noticed.

Quote:
By all means it looks like bug in x1000 (only?) installation CD.


Yeah, you could consider it a bug. I mean, without it the system won't boot. You got stuck on it.

It's really no different to what was needed in my X1Boot Linux installer I released last year. That needed to scan all partitions on all HDD drives for a compatible FFS partition. Same process but using foreign Linux tools to do it.

So natively on the OS, with native tools and API, I don't see much reason for excuses in this area.

Quote:
Anyway, step by step i relaize why they go X5000 route : Cyrus boards for sure much better , not only because of DDR3 vs DDR2, but all those tasty things, like inbuild rs232 on rare of motherboard, like booting from USB possible (very big deal should to say), or like default way to have in the microSD card uboot/amigaboot.of.


RS232 would be design thing I suppose. It's there but you need the external port for it.

The X5000 is quirky as it has both firmware and boot loader on micro SD. This means it's always needed and the boot loader won't even be loaded from HDD. Aside from firmware you can store amigaboot.of on CF so it's similar. Of course, like serial, CF was an option. So you need to BYO unless you had the full case set up.

I just bought the board, optioned on serial, and don't ever recall using the CF slot. Suppose needing an extra disk to plug in just seemed a hassle. I just left USB stick in my keyboard.

Quote:
The only thing which i for real like a lot, and what Cyrus didn't have : is this good tasty graphical kind menu on booting which you can navigate with case up/down. X5000 menu looks realy bad in compare. X1000 one looks like "amiga", while Cyrus one looks like "another not adapted enough menu". Dunno what the reassons were to go that route, and didnt' create the same good menu as on X1000.


That's interesting. I've only seen pictures but my impression was that the X5000 looked more Amiga like with the Gadtools early startup look in the menus. The X1000 looks nice. But it doesn't look like Topaz to me.

Quote:
Ah, and USB copy for crossdos : on x1000 and sam460 it fast. On x5000 slower much. There were something in usbstack i remember like "we reduce the speed, because it bring bugs", but that just about software side. But i need to test it all once done with finetuning Nemo, maybe something changes already in beta drivers.


Didn't know that. Not reduced to USB 1.1 speed? Unimaginable! Well, USB on OS4 has always had bugs. I have to drop the speed down from 2.0 to 1.1 on my VIA USB card in my XE currently as it crashes otherwise. But that's being investigated now.

Last night I had an annoying time trying to write a booter. So I grabbed my install CD. Was going to use RawWrite to create a CD image but it wouldn't do that. So I used AmiDVD to image it in RAM. Then mounted it. Copied it to RAM so I could modify the contents and write back. Something went wrong and it froze. I suppose this is because of the new RAM Disk bug where it was thought a whole system freeze is better than an out of memory error. It's supposed to use extended memory. I don't have much hope in that. I have 4GB installed and it can't even handle 1.2 GB of data in 2GB RAM.

So I thought I would quickly format USB as FFS and quickly copy over a test volume. Big mistake pal! 3/4 through writing it just froze randomly.

Next I tried FFS boot and SFS Workbench. It finished doing that. But it was weird with SFS. It kept "thinking" with a clock pointer. It didn't do that with FFS. So tested that, but I couldn't get it to work. CFE kept having trouble finding the boot loader off USB. And when it did load it didn't see the SFS volume.

Next thought I would just image CD direct to USB. I used RawWrite. But made a mistake. RawWrite cannot be used to write a full image to USB because it wants a DOS device. I wrote it to first device on USB but in CFE it just couldn't see it. Then I realised I had written a CD image to an offset on disk as it had an RDB and I wrote to a partition!

We need proper USB tools. We need a USB image writer which we don't have. I didn't know USB was so bad on OS4. We need Format to not ghost itself and always load so we can pick a disk and always format it to a format of our choice. As it stands we cannot format USB disk from OS4 as either FAT or NTFS because there is no tool to do it and the hidden commodity for the job, with no tool or icon anywhere, is broken again and can't do it. Seriously why is the mass storage commodity always broken? Useless!

So somehow I managed to create a recovery image. I used FryingPan as it can use CD as source and substitute files. But the interface is quirky and annoying to work with. It does however work. I would have preferred AmiDVD as it's simpler but OS4 would freeze again if I tried to modify files in RAM then image it out to RAM.

So created a booter iso image and back to CFE. CFE won't load disk from tower USB port. Typical. Stick in my keyboard. Loads. I somehow forgot about this CFE bug, it can read USB sticks, but it cannot mount them so they don't work.

Manage to get CFE to load the boot loader! It's looking up! AmigaBoot loads! It scans! It's missing my USB stick!! Arghhhh!!!!!

I bet I know what it is. The CD image wasn't set as bootable. I don't know if and where FryingPan can do that. I've used a Linux app that can when I built the Debian Jessie installer image which was a tad easier than Frying Pan. So looks like I will somehow need AmiDVD if FryingPan can't create a bootable image.

One of these days, if I ever get to it after shelving new projects I started, I will write my own USB booter. Recovery image creator. But I need to learn ReAction first. Or it will be scripted from DOS.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quick answer. Yes you need a boot volume for amigaboot.of. Thought I may have mentioned that in one of my big posts last page.

If you have a spare CF card you can format as FFS2 and stick it there but you will need to change CFE boot line. So it loads cf0:amigaboot.of instead.

Otherwise, backup then create a boot volume and Workbench again. Be great if you could resize/move a volume or even copy to RAM, insert volume, format then copy back.

As you found out OS4 is rather ignorant at times because it wasn't programmed to do proper checks for a boot loader. I brought this up about amigaboot.of being a file that needs a boot volume instead of an SLB you install in. I was told it's easier for them to copy a file than the SLB way. It doesn't matter how it's done, what matters is MTB sets it up.

Later there was some BOOT volume convention but it was too late. Now, MTB should have created this itself, as part of the install process. Why doesn't it create a boot volume as part of the HDD install process and copy amigaboot.of there? Problem solved!

No, MTB is not logical. What do we expect? It selects DOS3 for you when DOS7 is the only supported FFS for OS4. Many people got caught on that one. This was meant to be a quick reply.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
I do use one which is in the latest x1000 iso : amigaboot 53.4 (19.11.2010).


Ouch. Almost 12 years old. They left that on the X1000 FE CD?

Quote:
Did i understand right that you saying that more fresh amigaboot are able to make x1000 to boot from usb with this "-fs=iso atapi0.1:amigaboot.of" ?


Sorry no, I can't confirm that, it's just V1.0 is really old. So if it was going to work a newer one would be needed.

Quote:
Maybe that was it ?


Aha. Yes that looks better. So it has a hardware limitation of 512 bytes per block? Don't know if USB sticks have more. A CD uses 2048.

Can check from MTB from Install screen.

Quote:
I use radeonHD 250 or something, and while do tests with CD booting, it at least go the the level showing me all the windowses and co.


R5 250? It must be supported by lite driver then.

Quote:
So far X5000 looks for real better than x1000. I of course do get x1000 for own reassons and testing, but for users for sure better to get x5000 , at least for those reassons:


Yes, if the X5000 had AliVec, it would kill the X1000. Not that I use vectors much but they can help in some applications. The X1000 may still hold its own in some CPU operations.

The X5000 looks more user friendly. The X1000 still has boot menus that can be configured. But there is no menu editor to do it so there's some work involved.

The serial out was an option but I guess only beta testers optioned that on. I did. But it needs to be mounted on a back panel.

By accounts it also boots faster. You would have noticed how slow the X1000 is to boot. An XE would make it look silly. I don't know if the X5000 has much a delay bringing the video card up but on the X1000 it will be 10 to 15 seconds just to bring up the video card for the logo. After that it then wastes more time doing I don't know what. Finally it starts reading the HDD! By the time my X1000 starts loading OS4 my XE had booted to Workbench 20 seconds ago.

Quote:
But i do have HDD for now on Sata0, and cd-drive on Sata2, and so loading of installation cd take for real 5-7 minutes, maybe 10. That why i want to install from USB.


You do have the drives on the standard ports. That's too long. It shouldn't be that slow. How recent is your CD drive? A DVD drive shouldn't take that long. I have Bluray drives and it wouldn't take too long.

It will take its time loading Kickstart as it likely uses PIO 0 or something. But after that it should speed up. DMA should be activated when DOS kicks in.

Quote:
I were under opinion that i made USB boot to work just by create my own X1000 CD, with newer Amigaboot.of, but that was falsely positive, because it just loads up from my HDD.. Damn..(i just have left kernel moduels and stuff when testing CD installing)


Damn. I was getting excited. So I did a test last night. Man, USB on OS4 is still buggy! First I tried to format from the mass storage commodity. Doesn't work. Then I tried something else and it took down the system. Had to reboot. This reveals another X1000 flaw. You have to constantly keep a serial cable connected or you miss crash logs. For some reason they broke the debug bugger on the X1000. When you soft reboot you lose the buffer so there goes your crash report!

So I created a FFS2 volume from MTB to test and was copying my test volume to it. Thought I would give fs_plugin_cache a go. Still slow. Then the classic AddBuffers. Oops wrecked it. System freeze!

Wiped it all off and then set it up with FFS2 for boot and SFS for WB. Back to CFE and couldn't get it to work. CFE is too fiddly. It's good you can do a dir but you need to know filesystem as it doesn't know or check itself. Tiring.

I found also it didn't mount my stick. But did mount it in my keyboard. Seriously!

Come to think of it I may have forgot to write the bootloader on. I'll test again. And then try with a CD image.

Quote:
So seems amigaboot.of still can't find bootable USB stick, sadly. It brings exactly the same issue even with latest amigaboot.of, and crashes the same after.


Something is wrong there. I'm sure I read about that bug being fixed. ATM amigaboot.of is also on uncertain terms because since ExecSG changed ownership it's now in the hands of AEON. So the latest version available is 54.0 on my system. Apparently Trevor wrote it.

What is your CFE variable amigaboot_quiet set at? Should be set to N so you get a boot menu.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
So as can be seen it load amigaboot.of, but then says "No bootable devices found", and reboot.


It crashed! That version looks really old. V1.0. You should have at least amigaboot 53.21 (13/06/2016).

Lately this is taken by AEON but either one should be better. I'll find a USB stick I can scrap. And do some testing later on.

Quote:
if you poweron machine with already inserted USB in, then CFE didn't see it. You need to plug off and plug on usb stick to make it be visibly for CFE.


Yeah that's normal. I didn't see it much because I left a USB stick in my Apple keyboard that was detected when I wanted to boot Linux from it. So a work around could be to use a hub or it could really be that CFE only scans the USB keyboard port which is why it worked for me. So you may need a hub connected to keyboard port so it detects it. Yes another annoying quirk.

Quote:
Why i need updated drivers for OS4 installation CD ?


Because if you boot a standard CD, like FE, you will get a black screen if you have something like a HD6000 or newer.

I don't recall what model breaks, I had a HD5450 that worked, but at some model they won't work. Because the RadeonHD lite driver is depreciated and isn't updated anymore. Unless you have an old card, that also lacks 3d support in the process, it won't boot.


I fail to find a specific list of supported cards in the lite driver. All I know is my FE CD doesn't with my R7 250.

Quote:
Maybe i can use 2 sticks, like one to boot amigaboot.of from it, and another with installation data ?


You could, but only if your HDD breaks. You could also just let it load amigaboot.of off HDD and then find USB. Of course if no amigaboot scans for USB then the whole idea is pointless and it really then cannot boot off USB no matter what you do.

The easiest way to test would be to copy a boot volume to a USB drive formatted as FFS2. Yes it will be slower over FFS2, unless you enable caching with the now old FFS cache commands. But CFE can load a binary off FFS2. Anything else is not Amiga format so complicates it.

You must be annoyed by now at searching for X1000 USB boot and only getting result X5000 USB boot or how easy it is to create a USB booter.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

It should be able to autoboot USB if you modify the boot commands. Just like on the XE. But that is a different beast.

As standard it's set up to boot from either CD or HDD with no user intervention.

You could add boot commands to the main boot line. That tries to boot USB, then HDD. And just fallback or in this case if the USB boot falls it will just execute the next command.

But try this. Grab a spare USB stick you can wipe, then using RawWrite or any USB image writer, write the OS4 CD image directly to the disk. Now reboot and enter this:
boot -fs=iso usbdisk0:amigaboot.of


You will of course need updated drivers. So a CD image would need to be rebuilt for that to work. In that case, another way, use an Amiga format to simply copy files too. So format a USB stick as FFS from the USB commodity (fastest) or from MTB (slowest). Then copy the Workbench files and updated drivers to it. Reboot and try this:
boot -fs=amigafs usbdisk0:amigaboot.of


If it doesn't like that combination of mixed media and filesystems you shouldn't need two USB sticks to do it. Just partition a stick with boot volume and main volume. So FFS for boot with bootloader and SFS for main with Workbench.

CFE does support FAT32 but it has it's quirks. As stated before it can be picky and files go missing or it gives errors. It's also old so it may not support FAT32 on a 64-bit size disk since an 8GB stick is 64 bit range.

As to CFE not having help for amigafs. It probably wasn't updated internally. But they are supported as without it Amiga OS4 wouldn't boot!

Go to top


Re: LiteXL v2.1.0 is released
Just popping in
Just popping in


@kas1e

You have a long memory. I thought about this last week, yesterday and now today! What you are likely referring to could be something from ten years ago on my XE. In simple terms it would be obsolete. I recall something from a July 2007 update and being unable to fully use that or some other update, as it broke some 68K software. So had to leave an older OS install to use that particular software. This was not unusual in the early days.

However, since then, I moved over to the X1000. And set up my volumes again in the process. As you would be aware I'm also a beta tester so do have a few volumes with different OS4 versions. I have test volumes I keep clean though tend to only test system software on them. I do find it would help if developers tested software on a base system as I find some software can easily break on a base install and can tell if it was only tested on the developers full system.

My personal Workbench would not be fully up to date. Because I still need to run the Update 2 Quckfix as I call it, with an Update 1 kernel and Update 2 components. This is not by choice, but simply because Update 2 is incompatible with my Sapphire R7 250, and compositing freezes my system. Until the conflict is found there is not much else I can do about this on top of the months I've been investigating it. My other options are going back to a HD5450 with no 3d support or disabling compositing. I don't like either of these options and just like to get work done on my system. So until the problem is found my own Workbench will remain in this quantum state.

Go to top


Re: LiteXL v2.1.0 is released
Just popping in
Just popping in


@walkero

Quote:
Thank you for testing it. Did you create a new installation? Did you use the old .config/litexl folder? If yes, please try to remove it and try again. This should be either under the LiteXL folder or under the HOME folder, if you have that environment variable set.


I tested it fresh. I didn't use an old config. What I did was fairly simple and this may give a clue. I do it with all new and updated software I test. I simply extract the archive to my RAM disk. And run it from there!

I checked and I don't have a HOME folder variable set.

Quote:
Also, please let me know the full path you run LiteXL from.


That would be "RAM Disk:LiteXL2".


I'll submit a report on git. I also found in the OS4Depot crash reports that TearsOfMe also has a crash on his X1000. But the crash is different.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


@kas1e

Quote:
As i have all version of CFE binary on my other computers, for me it just matter of read the binary in any editor. And i have all the answer about anyway, latest version is : "Fri Jun 8 16:04:49 CEST 2012"


Yes I saw that. That would be the easy way if you have a CFE binary. Otherwise if you are checking CFE from a live X1000 you can dump the firmware to find the build.

Ranger can also show firmware information. Not sure but it may also be able to find the build date. It can list NVRAM settings.

Quote:
As for settings : yeah, probabaly pulling out the battery will be the best choose, as i remember reading somewhere that this "jumpering CMOS clear" can be used as last one as can cause problems.


I'm usually afraid of loosing settings when changing battery. Only done it once on my X1000 IIRC. I've not tried the jumper as my settings have not corrupted.

It's slight manual setup but there is one way you could do it. After you "clean the slate" you could save settings and write a batch script to restore it. Using a serial debug grab the NVRAM settings. Now convert all the settings into a batch file that can reset them with setenv commands. Best to set them all of them locally then on the last line issue command to save to NVRAM.

The only caveat is it won't remove newer variables set up. But the method can be used to reset standard ones or even save what you have. Yes pulling battery easiest to do!

As is becoming common NVRAM can only be read from OS4 and not written. Don't know why. Makes the XE look like a luxury given it can write from OS4. So not an OS4 app could be written to reset NVRAM.

I suppose if it was known what's needed to write to NVRAM from OS level this restriction could be removed.

Go to top


Re: x1000 documentation and other x1000 related questions
Just popping in
Just popping in


Didn't see this mentioned but while on the CFE subject.

Strange CFE errors:
Sometimes you may see strange or non-sensible errors pop up in CFE. A common one is CFE dropping out when booting and saying it has "Insufficient memory" when failing to load amigaboot.of.

This can be caused by a glitch in SATA cables. It was a common error in the early days. The rest of us are used to these quirks by now.

It's also covered below in the X1000 wiki guide:
https://wiki.amigaos.net/wiki/AmigaOne_X1000

Go to top


Re: LiteXL v2.1.0 is released
Just popping in
Just popping in


@walkero

Thanks. Unfortunately it still broke again. Same thing. Reaper gave me an 81000009 free mem twice guru again.

I thought it may be a missing HOME variable but I don't see it look for one.

I got out Snoopy. The last thing it does is UnLock("lite-xl") and then Reaper takes over. Up to then it goes fine opening and examining files. Suppose I should grab a full log.

Go to top



TopTop
« 1 ... 8 9 10 (11) 12 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project