@trixie

Quote:Not you, silly, you have far better things to do than operating my PC .

Best regards,

Niels

@Tuvok

Here are my CFE vars - nothing in there that I think could have any influence, but just in case.



And I am using that port for the USB cable coming from the KVM switch, so both keyboard and mouse are seen through that cable, and there is a KVM switch in between.

I'm not sure that comment in the manual should necessarily be taken as the golden truth, for instance I guess KVM switches behave differently, so some may be causing problems, while others manage to seem transparent to the system.

But I'm no expert. Perhaps Graff knows more.

Best regards,

Niels

@khayoz

Yes, of course (although technically SYS: is an assign itself, only made by the system during startup).

My point was more for completeness, to state that the device name of the first disk is not necessarily DH0:

But I'm getting nerdy ...

Best regards,

Niels

@rjd324

Sorry, no idea. I would expect a USB cable to be a USB cable, though.

But I've only ever bought the ATENs new, and those came with all connector bundles needed.

Best regards,

Niels

@rjd324

Yes.

That's what I'm doing, see the above description for the X1000. My X5000/40 is connected to port 3, and in port 2 I have a pc dual-booting Debian and Win7Pro.

I do have the issue that after having used Debian Linux and returning to AmigaOS or Windows, I have to pull the mouse receiver out of the KVM switch for some seconds and re-insert it, because until I do, the mouse pointer won't move. The keyboard is not affected.

This is probably something Debian does, because it wasn't always so. I think it started after upgrading Debian to Bookworm. I intend to upgrade it to Trixie soon, we'll see if it changes things.

But as for X1000 and X5000, I have no problems. Keyboard working fine in UBoot/CFE as well.


Best regards,

Niels

@AmigaOldskooler

Thanks for the roundup, enjoyable reading as always.

And especially thanks for implementing the suggestion about using a still picture to link to a video, instead of having to load the full video for each one.

The full page loads so much faster now!

Best regards,

Niels

@walkero:

I can confirm it happens for me as well. I just tried to view your profile, and it shows my own instead with the message quoted earler.

Best regards,

Niels

@khayoz

Quote:More correctly, it works if your boot drive has a volume name of System: (or if you have in fact created an assignment called System: pointing to SYS:).

There's no requirement that its device name must be DH0: (mine is actually DH1: on my X1k, as I have a small partition with device name DH0: containing amigaboot.of).

Best regards,

Niels

On the X1000, the USB part of the cable to the KVM switch is in the lower port of the first column (i.e the one closest to the sound sockets).

I'm not sure what the USB port dedicated for the keyboard is on the X1000, isn't that just one of two in the first column? There are (IIRC) no markings of where to connect the keyboard on the X1000 backplate.

The other end of the cable is connected to port 4 of the KVM (USB, DVI DL, and sound play/rec).

My mouse (receiver) is in the keyboard socket on the back of the KVM.

My keyboard is in the USB2.0 socket below the mouse and keyboard sockets on the back of the KVM.

And yes, I can use the keyboard in CFE.

Best regards,

Niels

@Tuvok

Thanks for the heads-up.

I think maybe my firmware is already 1.0.077 or more, because the buttons seem to already function like that for me. Now that you mention it, I remember reading something about it before.

At some point when I get time, I will try checking my KVM switch's firmware version and also update it to the latest firmware, but that will probably not be until some time in the new year.

As for why it works so strangely on your X1000, I don't know. I don't see such behaviour on mine. But I'm no "Voodoo master" .

Best regards,

Niels

@AmigaOldskooler

Or maybe you could just take a screen shot of the first frame and use that as the image link - that should look almost like now without the memory usage.

Best regards,

Niels

I agree, nice work - as usual.

I do have one wish, though: Would it be possible to make simple links (picture links, for example) to all those YouTube videos instead of imbedding the full videos directly into the page? As it is, this month I couldn't even load the page in Odyssey on my X1000 with 2GB. I had to f*ing start a W* pc ...

Best regards,

Niels

@graff

And I never thought about upgrading the firmware of the KVM switch, should probably try that some day when I feel lucky .

Maybe the newer firmware would even let me put my keyboard back where it was meant to connect? You never know (unless you try).

Best regards,

Niels

@Tuvok

I use a CS1784A with some of my machines also, including an X1000.

I have found that it works best if I connect the keyboard not to the socket with a keyboard symbol, but to the "generic" USB socket below that on the back of the KVM switch. I have the mouse receiver for my wireless mouse (Logitech) in the keyboard socket. And I don't know if it matters, but I currently have the X1000 connected to the 4th section of sockets.

Also, I have found that you have to experiment a bit to find the best way of pressing the switching buttons to make sure the USB is also switched; my technique at present is a short press on the middle of the button (on the little groove).

Best regards,

Niels

Yep, like @NinjaCyborg says.

For an example, I do it like this in one of my scripts:

set dt `C:Date LFORMAT "%Y%m%d%H%M%S"`

PS. You can edit the LFORMAT string to your wish, e.g. putting your underscore between the %d and the %H.

Best regards,

Niels

@balaton

Quote:
and

Quote:
Yes, you're right, and I think I may have been carried away down the road of defending "the Amiga way". Maybe what triggered it was that I read an opinion into it that "AmigaOS is silly because it maintains case insensitivity, while mainstream OSs don't" or something. That tends to ignite the defensive side of me .

In fact, thinking about your specific issue, it might be reasonable to expect users who use a particular host OS with case sensitive file system(s) to know about this and take the consequence of making sure the files going into the .zip have correct casing. Even if they are using Kyvos to help them with the setup.

BTW, I don't use QEMU/BBoot or Kyvos myself (I have enough real Amiga NG hardware), but I find it interesting to read about users doing it and about the possibilities and challenges they meet.

Best regards,

Niels

@balaton
Quote:
Never!

Quote:There was actually - I believe some file systems (ported from elsewhere?) could be set to be case sensitive under AmigaOS, but noone uses that feature, as the rest of the system isn't made to expect such a non-Amigaish feature.

Quote:Well, it shouldn't, then. I'm not sure if all ports of Unzip are the same, but at least the Amiga one has the modifier "-C match filenames case-insensitively".

Best regards,

Niels

@joerg
Quote:
I think it was actually that way in all generations of AmigasOS. My first one was an A500 with v1.3 (in 1989), and it was certainly case insensitive.

It's "a feature, not a bug" - part of what makes AmigaOS helpful for users, not making users having to help the system.

Best regards,

Niels

@MazinKaesar

Update 3 installs AmiSSL 5.25 - I believe it is still the latest.

An installation log is not saved by the OS4 Installation Utility (unlike what you can choose to do with the Installer).

Edit: BTW, I would be very surprised if AmiSSL had anything to do with the network driver working or not.

Best regards,

Niels

@MazinKaesar

I just checked on my Sam460LE, I don't have the problem.

I set my PubTest partition (the one I used to test the various beta versions of Update 3 up to the release) back to its initial state, i.e. with Update 2 and the other later small updates. Then I installed the publically released Update 3 (fetched from my account at Hyperion's page) and let it reboot, and the network came up with no problems.

Best regards,

Niels