On 30/12/2023 14:29, Tim Streater wrote:
> On 30 Dec 2023 at 12:19:37 GMT, "The Natural Philosopher"
> <tnp@invalid.invalid> wrote:
>
>> On 30/12/2023 09:37, Tim Streater wrote:
>>> Other things being equal, and if
>>> you have no other traffic, and you have an end to end connection that is made
>>> up of sections running at diffeent transfer rates, the end to end transfer
>>> rate will ramp up until the slowest link is saturated. At which point it
>>> starts dropping packets,
>>
>> No, what will happen is that ACKS will be very delayed, and no further
>> packets will be sent until the ACKS from previous packets have been
>> received.
>
> My explanation was good enough for government work. The salient point is that
> there is end-to-end flow control so the speed and type of intermediate links
> doesn't have to be known by any equipment other than what the links are
> connected to.
>
Your explantion implied dropped packets. That simply isn't the case
these days. TCP/IP is mostly auto-throttling . Dropped packets lead to
disaster. Endpoints will retransmit
massively increasing traffic and congestion

>> Dropped packets only happen when one end keeps stuffing packets into a
>> link that cant buffer whats its sent.
>
>

--
The higher up the mountainside
The greener grows the grass.
The higher up the monkey climbs
The more he shows his arse.

Traditional

On 30/12/2023 14:34, Tim Streater wrote:
> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
> <tnp@invalid.invalid> wrote:
>
>> On 30/12/2023 09:41, Tim Streater wrote:
>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>> <tnp@invalid.invalid> wrote:
>>>
>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>> Apple is renowned for ignoring any standards but its own.
>>>
>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>> DHCP problem.
>>>
>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>> frequency, protocols, security protocol.
>>
>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>
>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>
> And which Safari version is that?

All of them

Even firefox on a MAC wont play, because the decode libraries simply
don't exist on a MAC.

Apple simply doesn't think its that important to fix. Not Invented Here.

--
“when things get difficult you just have to lie”

― Jean Claud Jüncker

On 30/12/2023 12:23, The Natural Philosopher wrote:

> Apple is the platform that invented firewire, used by no one else.

Not quite true, and it's a shame it wasn't used more. In 2001 bought an
Epson 2450 scanner which came with Firewire and USB2 ports. Fortunately,
my (new XP) computer came with a Creative sound card which for some
reason had a Firewire port. I used that with the Epson. When I tried
using the USB2 port instead, I couldn't believe how slow it was compared
to Firewire.

--

Jeff

On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
<tnp@invalid.invalid> wrote:

> On 30/12/2023 14:34, Tim Streater wrote:
>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>> <tnp@invalid.invalid> wrote:
>>>>
>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>> Apple is renowned for ignoring any standards but its own.
>>>>
>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>> DHCP problem.
>>>>
>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>> frequency, protocols, security protocol.
>>>
>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>
>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>
>> And which Safari version is that?
>
> All of them
>
> Even firefox on a MAC wont play, because the decode libraries simply
> don't exist on a MAC.
>
> Apple simply doesn't think its that important to fix. Not Invented Here.

I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
I'm on Catalina which is about 4 versions back from the latest OS version.

So I copied the .webm file to my fileserver, which is running Monterey (only
two versions back). There, Safari played it without issue.

--
There is nothing a fleet of dispatchable nuclear power plants cannot do that cannot be done worse and more expensively and with higher carbon emissions and more adverse environmental impact by adding intermittent renewable energy.

On 30/12/2023 12:23, The Natural Philosopher wrote:
> On 30/12/2023 09:41, Tim Streater wrote:
>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>> Apple is renowned for ignoring any standards but its own.
>>
>> Rubbish. The early iPad must have had a bug in its DHCP software,
>> subsequently
>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever
>> has a
>> DHCP problem.
>>
> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
> frequency, protocols, security protocol.
>
>> And I'll think you'll find it's MS which has frm in ignoring standards.
>
> Er no. Apple is the browser that STILL cannot deal with Webm video
> protocols
> Apple is the platform that invented firewire, used by no one else.

My Nikon Coolscan slide scanner (only) uses firewire

On 31/12/2023 09:36, Tim Streater wrote:
> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
> <tnp@invalid.invalid> wrote:
>
>> On 30/12/2023 14:34, Tim Streater wrote:
>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>> <tnp@invalid.invalid> wrote:
>>>
>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>> <tnp@invalid.invalid> wrote:
>>>>>
>>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>
>>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>>> DHCP problem.
>>>>>
>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>> frequency, protocols, security protocol.
>>>>
>>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>>
>>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>>
>>> And which Safari version is that?
>>
>> All of them
>>
>> Even firefox on a MAC wont play, because the decode libraries simply
>> don't exist on a MAC.
>>
>> Apple simply doesn't think its that important to fix. Not Invented Here.
>
> I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
> I'm on Catalina which is about 4 versions back from the latest OS version.
>
> So I copied the .webm file to my fileserver, which is running Monterey (only
> two versions back). There, Safari played it without issue.
>
Not if its encoded vorbis/VP8

--
“Progress is precisely that which rules and regulations did not foresee,”

– Ludwig von Mises

On 31 Dec 2023 at 12:13:43 GMT, "The Natural Philosopher"
<tnp@invalid.invalid> wrote:

> On 31/12/2023 09:36, Tim Streater wrote:
>> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> On 30/12/2023 14:34, Tim Streater wrote:
>>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>>> <tnp@invalid.invalid> wrote:
>>>>
>>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>
>>>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>>
>>>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>>>> DHCP problem.
>>>>>>
>>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>>> frequency, protocols, security protocol.
>>>>>
>>>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>>>
>>>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>>>
>>>> And which Safari version is that?
>>>
>>> All of them
>>>
>>> Even firefox on a MAC wont play, because the decode libraries simply
>>> don't exist on a MAC.
>>>
>>> Apple simply doesn't think its that important to fix. Not Invented Here.
>>
>> I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
>> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
>> I'm on Catalina which is about 4 versions back from the latest OS version.
>>
>> So I copied the .webm file to my fileserver, which is running Monterey (only
>> two versions back). There, Safari played it without issue.
>>
> Not if its encoded vorbis/VP8

The video I downloaded as mentioned above, apparently needs the Google-On2 /
VP8 codec. How does that differ from the vorbis one? Provide me with a
vorbis/VP8 example.

--
27/6/1975 - Herbert Kiebler shot and killed trying to cross Berlin Wall.

"A reminder that the defining characteristic of a socialist regime is coercion, not equality."

Dan Hannan

On 31/12/2023 12:51, Tim Streater wrote:
> On 31 Dec 2023 at 12:13:43 GMT, "The Natural Philosopher"
> <tnp@invalid.invalid> wrote:
>
>> On 31/12/2023 09:36, Tim Streater wrote:
>>> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
>>> <tnp@invalid.invalid> wrote:
>>>
>>>> On 30/12/2023 14:34, Tim Streater wrote:
>>>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>>>> <tnp@invalid.invalid> wrote:
>>>>>
>>>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>>
>>>>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>>>
>>>>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>>>>> DHCP problem.
>>>>>>>
>>>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>>>> frequency, protocols, security protocol.
>>>>>>
>>>>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>>>>
>>>>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>>>>
>>>>> And which Safari version is that?
>>>>
>>>> All of them
>>>>
>>>> Even firefox on a MAC wont play, because the decode libraries simply
>>>> don't exist on a MAC.
>>>>
>>>> Apple simply doesn't think its that important to fix. Not Invented Here.
>>>
>>> I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
>>> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
>>> I'm on Catalina which is about 4 versions back from the latest OS version.
>>>
>>> So I copied the .webm file to my fileserver, which is running Monterey (only
>>> two versions back). There, Safari played it without issue.
>>>
>> Not if its encoded vorbis/VP8
>
> The video I downloaded as mentioned above, apparently needs the Google-On2 /
> VP8 codec. How does that differ from the vorbis one? Provide me with a
> vorbis/VP8 example.
>
I cant be arsed. I know because I spent days trying to make this work,
that there isn't a decoder for apple

--
The lifetime of any political organisation is about three years before
its been subverted by the people it tried to warn you about.

Anon.

On 31/12/2023 13:52, The Natural Philosopher wrote:
> On 31/12/2023 12:51, Tim Streater wrote:
>> On 31 Dec 2023 at 12:13:43 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> On 31/12/2023 09:36, Tim Streater wrote:
>>>> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
>>>> <tnp@invalid.invalid> wrote:
>>>>
>>>>> On 30/12/2023 14:34, Tim Streater wrote:
>>>>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>
>>>>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>>>
>>>>>>>>> If it doesn't work at all, then the wifi isnt working, or at
>>>>>>>>> most the
>>>>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>>>>
>>>>>>>> Rubbish. The early iPad must have had a bug in its DHCP
>>>>>>>> software, subsequently
>>>>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has
>>>>>>>> ever has a
>>>>>>>> DHCP problem.
>>>>>>>>
>>>>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>>>>> frequency, protocols, security protocol.
>>>>>>>
>>>>>>>> And I'll think you'll find it's MS which has frm in ignoring
>>>>>>>> standards.
>>>>>>>
>>>>>>> Er no. Apple is the browser that STILL cannot deal with Webm
>>>>>>> video protocols
>>>>>>
>>>>>> And which Safari version is that?
>>>>>
>>>>> All of them
>>>>>
>>>>> Even firefox on a MAC wont play, because the decode libraries simply
>>>>> don't exist on a MAC.
>>>>>
>>>>> Apple simply doesn't think its that important to fix. Not Invented
>>>>> Here.
>>>>
>>>> I went here <https://www.webmfiles.org/demo-files/> and downloaded
>>>> one of the
>>>> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't,
>>>> but then
>>>> I'm on Catalina which is about 4 versions back from the latest OS
>>>> version.
>>>>
>>>> So I copied the .webm file to my fileserver, which is running
>>>> Monterey (only
>>>> two versions back). There, Safari played it without issue.
>>>>
>>> Not if its encoded vorbis/VP8
>>
>> The video I downloaded as mentioned above, apparently needs the
>> Google-On2 /
>> VP8 codec. How does that differ from the vorbis one? Provide me with a
>> vorbis/VP8 example.
>>
> I cant be arsed. I know because I spent days trying to make this work,
> that there isn't a decoder  for apple

It works fine on my Windows PC using Firefox.

I recommend both. If you want to spend 'days trying to make this work"
then feel free to stick to Linux.

On 31 Dec 2023 at 13:52:06 GMT, "The Natural Philosopher"
<tnp@invalid.invalid> wrote:

> On 31/12/2023 12:51, Tim Streater wrote:
>> On 31 Dec 2023 at 12:13:43 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> On 31/12/2023 09:36, Tim Streater wrote:
>>>> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
>>>> <tnp@invalid.invalid> wrote:
>>>>
>>>>> On 30/12/2023 14:34, Tim Streater wrote:
>>>>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>
>>>>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>>>
>>>>>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>>>>
>>>>>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>>>>>> DHCP problem.
>>>>>>>>
>>>>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>>>>> frequency, protocols, security protocol.
>>>>>>>
>>>>>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>>>>>
>>>>>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>>>>>
>>>>>> And which Safari version is that?
>>>>>
>>>>> All of them
>>>>>
>>>>> Even firefox on a MAC wont play, because the decode libraries simply
>>>>> don't exist on a MAC.
>>>>>
>>>>> Apple simply doesn't think its that important to fix. Not Invented Here.
>>>>
>>>> I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
>>>> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
>>>> I'm on Catalina which is about 4 versions back from the latest OS version.
>>>>
>>>> So I copied the .webm file to my fileserver, which is running Monterey (only
>>>> two versions back). There, Safari played it without issue.
>>>>
>>> Not if its encoded vorbis/VP8
>>
>> The video I downloaded as mentioned above, apparently needs the Google-On2 /
>> VP8 codec. How does that differ from the vorbis one? Provide me with a
>> vorbis/VP8 example.
>>
> I cant be arsed. I know because I spent days trying to make this work,
> that there isn't a decoder for apple

Having read slightly more in Winky and elsewhere, I only see Vorbis mentioned
in the context of audio. And it was the VLC media player that gave me the
codec info I quoted. So maybe vorbis/VP8 doesn't exist. Certainly the
reference info on Winky put Google and On2 (whoever they may be) firmly in the
spotlight codec-wise.

If I'm referred to an actual vorbis/VP8 video file, which the VLC media player
can play but Safari on Monterey cannot, then I'll be minded to reboot my Mini
into Sonoma.latest, to see whether it can there.

Meanwhile I have evidently voided the contention that Safari on Monterey or
later, and Firefox on my becoming-ancient Catalina, can't handle WebM video.

--
"That which can be asserted without evidence, can be dismissed without evidence."
-- Christopher Hitchens

On 31/12/2023 13:52, The Natural Philosopher wrote:
> I cant be arsed. I know because I spent days trying to make this work,
> that there isn't a decoder  for apple

You can't be arsed to supply an example video to someone who might be
able to help you?

<fx shrugs>

Andy

On 12/30/2023 9:34 AM, Tim Streater wrote:
> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
> <tnp@invalid.invalid> wrote:
>
>> On 30/12/2023 09:41, Tim Streater wrote:
>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>> <tnp@invalid.invalid> wrote:
>>>
>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>> Apple is renowned for ignoring any standards but its own.
>>>
>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>> DHCP problem.
>>>
>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>> frequency, protocols, security protocol.
>>
>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>
>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>
> And which Safari version is that?
>
>> Apple is the platform that invented firewire, used by no one else.
>
> And they were the first to sell machines with USB, sold by no one else at the
> time

Come over to my place, and I'll show you the two "USB 1.1" ports on the G4.
And the smoking 1MB/sec transfer rate to an external drive.

Yes, at the time, I was pleased to discover that. Nice work.

Paul

On 12/30/2023 7:23 AM, The Natural Philosopher wrote:
> On 30/12/2023 09:41, Tim Streater wrote:

> Apple is the platform that invented firewire, used by no one else.

They used to add 1394 ports to PC motherboards, and this was the source of them.

VIA VT6315N IEEE 1394a port

It's not listed as Firewire in the user manual. The test machine has a 1394a,
and my two dead computers have 1394a as well. Likely never used on any of them
(don't have a camcorder). I used to turn it off at BIOS level, so not
even any driver would load for it.

I have two Firewire enclosures, the first in the chain ran at 30MB/sec,
the daisy-chained second enclosure (off the first enclosure) ran at 20MB/sec.
Not exactly a source of "shock and awe".

Microsoft has removed "Firewire networking" support from Windows,
but the other more popular interface options are still supported.
61882 might have been a standard for AV transfer from a Camcorder.
I don't know whether the mass storage one had a number like that
(since most PC users were doing camcorders with Firewire). A Google
search can't find any good info.

The Firewire networking, required a kind of router board if
you expected to do a subnet with it. You could still connect
two PCs together with a Firewire cable and set up a network
connection. But support for that is removed. Maybe it was still
working in WinXP days ?

I think if it got any traction, it was for the camcorders that
had a Firewire 4 pin connector on them (the two missing pins are
bus power).

Paul

On 31/12/2023 17:13, Vir Campestris wrote:
> On 31/12/2023 13:52, The Natural Philosopher wrote:
>> I cant be arsed. I know because I spent days trying to make this work,
>> that there isn't a decoder  for apple
>
> You can't be arsed to supply an example video to someone who might be
> able to help you?
I cant be arsed to provide a video to someone I know cant get something
to work that I don't need to work.

It was merely an example of apple incompatibility

--
“A leader is best When people barely know he exists. Of a good leader,
who talks little,When his work is done, his aim fulfilled,They will say,
“We did this ourselves.”

― Lao Tzu, Tao Te Ching

On 12/31/2023 4:13 AM, Jeff Layman wrote:
> On 30/12/2023 12:23, The Natural Philosopher wrote:
>
>> Apple is the platform that invented firewire, used by no one else.
>
> Not quite true, and it's a shame it wasn't used more. In 2001 bought an Epson 2450 scanner which came with Firewire and USB2 ports. Fortunately, my (new XP) computer came with a Creative sound card which for some reason had a Firewire port. I used that with the Epson. When I tried using the USB2 port instead, I couldn't believe how slow it was compared to Firewire.
>

If we assume the USB 1.1 transfer test ran at 1MB/sec, the engine
in the box (CCD based), seems limited to 2MB/sec. This is consistent
with the scanner I got back in the era. It was CCD and relatively
slow, and no amount of interface magic would make the engine go faster.
It needs exposure time per step on the stepper. Reducing the scan
resolution will help the scan finish faster. But if you compare
scan file size to the number of seconds to do the scan, the speed of the engine
should come out in the wash. I would expect engines like that
(CCD based single row) to manage 1-2MB/sec or so. It's possible someone
made a CCD or a CMOS element which was multiple rows, and may have overlapped
the scan to improve scan quality and speed. Some newer scanners used a camera
to "cheat" but then you need excellent pincushion correction to make a decent
scan. That's a little bit too much parallelism.

https://www.ephotozine.com/article/epson-perfection-2450-photo-4373

USB 1.1 300dpi A4 44sec 26Mb
USB 2.0 300dpi A4 23sec 26Mb

USB 1.1 800dpi A4 4min40sec 182Mb
USB 2.0 800dpi A4 2min 182Mb

USB 1.1 2400dpi 35mm Slide 3min 18Mb
USB 2.0 2400dpi 35mm Slide 3min 18Mb

"Regarding the USB cable that comes with the 2450 -- it is NOT USB 2.0 compliant.
I got one on ebay for about five bucks to go with the 2450 that I got at Sam's Club
(online) for $299."

Google is not coughing up a thorough enough test result.

With modern odds and ends available, I'd re-bench the thing, if it
still runs with the software we have today.

Firewire Networking was removed from Windows, but there are two other stacks for
Firewire that might still work (automatically). One should do AV transfers
from a camcorder, the other should do mass storage.

Motherboard docs identify Firewire as 1394a, so searching the PDF for
Firewire can be a waste of time. I checked the Test Machine, and the
manual only references a VIA 1394a chip (50MB/sec phy, slower transfers
when you do real things). USB2 is 60MB/sec phy and 30MB/sec mass storage
and 35MB/sec with UASP (USB Attached SCSI Protocol). The slowest USB2
ever made, that's an ATI Southbridge at only 20MB/sec. Might have been
SB400 or so. Can't find a reference in Google to verify.

Paul

On 31 Dec 2023 at 13:52:06 GMT, "The Natural Philosopher"
<tnp@invalid.invalid> wrote:

> On 31/12/2023 12:51, Tim Streater wrote:
>> On 31 Dec 2023 at 12:13:43 GMT, "The Natural Philosopher"
>> <tnp@invalid.invalid> wrote:
>>
>>> On 31/12/2023 09:36, Tim Streater wrote:
>>>> On 31 Dec 2023 at 09:02:40 GMT, "The Natural Philosopher"
>>>> <tnp@invalid.invalid> wrote:
>>>>
>>>>> On 30/12/2023 14:34, Tim Streater wrote:
>>>>>> On 30 Dec 2023 at 12:23:22 GMT, "The Natural Philosopher"
>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>
>>>>>>> On 30/12/2023 09:41, Tim Streater wrote:
>>>>>>>> On 30 Dec 2023 at 09:26:19 GMT, "The Natural Philosopher"
>>>>>>>> <tnp@invalid.invalid> wrote:
>>>>>>>>
>>>>>>>>> If it doesn't work at all, then the wifi isnt working, or at most the
>>>>>>>>> DHCP isnt working to issue the pad with a valid IP address etc.
>>>>>>>>> Apple is renowned for ignoring any standards but its own.
>>>>>>>>
>>>>>>>> Rubbish. The early iPad must have had a bug in its DHCP software, subsequently
>>>>>>>> fixed in later ones. Bit that's iPads. No mac I've ever used has ever has a
>>>>>>>> DHCP problem.
>>>>>>>>
>>>>>>> Maybe. Maybe not,. There are many variables in Wifi and DHCP -
>>>>>>> frequency, protocols, security protocol.
>>>>>>>
>>>>>>>> And I'll think you'll find it's MS which has frm in ignoring standards.
>>>>>>>
>>>>>>> Er no. Apple is the browser that STILL cannot deal with Webm video protocols
>>>>>>
>>>>>> And which Safari version is that?
>>>>>
>>>>> All of them
>>>>>
>>>>> Even firefox on a MAC wont play, because the decode libraries simply
>>>>> don't exist on a MAC.
>>>>>
>>>>> Apple simply doesn't think its that important to fix. Not Invented Here.
>>>>
>>>> I went here <https://www.webmfiles.org/demo-files/> and downloaded one of the
>>>> Big Bunny demos. Firefox 121.0 played it just fine. Safari didn't, but then
>>>> I'm on Catalina which is about 4 versions back from the latest OS version.
>>>>
>>>> So I copied the .webm file to my fileserver, which is running Monterey (only
>>>> two versions back). There, Safari played it without issue.
>>>>
>>> Not if its encoded vorbis/VP8
>>
>> The video I downloaded as mentioned above, apparently needs the Google-On2 /
>> VP8 codec. How does that differ from the vorbis one? Provide me with a
>> vorbis/VP8 example.
>>
> I cant be arsed. I know because I spent days trying to make this work,
> that there isn't a decoder for apple

<https://caniuse.com/webm>

See, it's not just me that says that WebM is now fully supported by Apple.

--
"It is hard to imagine a more stupid decision or more dangerous way of making decisions than by putting those decisions in the hands of people who pay no price for being wrong." -- Thomas Sowell