@kas1e

FYI, AmiVNC is open source.

I've been using AmiVNC for years... Yes, it's slow and highly
dependent on net bandwidth and the efficiency of the VNC client.

It used to work flawlessly with the RealVNC client until RealVNC
"improved" their client. The ChickenOfTheVNC client on the PPC
Mac still works great with AmiVNC (if slower).

There's a slightly updated version of AmiVNC where the color
issue was improved by Broadblues (Thanks!). I'd need to check
with him to spread it around.

FWIW, there's also another (new, from scratch) VNC server in
works that I'd expect will break the surface soon. So far it's
faster than AmiNVC.

Stay tuned.

Thanks,

PJS

@ktadd

I don't know why you'd post remarks about a MattyOS bug on the
comments section of the YT.rexx.

Either uninstall MattyOS and run AmigaOS *OR* get Matty to fix
his hack job.

Good luck,

PJS

@ktadd

LOL

Thanks again for your work on this.... I look forward to your
next version.

PJS

@ktadd

That's a fantastic script!

@Maijestro

Great video!

I wanted to pass along one little hack I had already put in my
start_player script that lets me run streams in a single ongoing
player (instead of starting a new one each time you click "PLAY"):

Where it used to just call AmigaAmp like this:

---
Run <>NIL: APPDIR:AmigaAmp3 "{url}"
---

I replaced it with a test of whether AA had an ARexx port open
and send it an ARexx message to load the new stream instead,
like this:

---
WaitForPort "AMIGAAMP" 0
IF WARN
Run <>NIL: APPDIR:AmigaAmp3 "{url}"
ELSE
rx 'ADDRESS AmigaAmp "OPEN {url}"'
ENDIF
---

Fodder for an update if you'd like to include it in your script.

Thanks guys!

PJS

@walkero

Yay!

What a great developer!! Only on an Amiga!! You fixed it
without even doing anything!

;D

PJS

ahh, yes, same here!

If I click on "Popular" or "Trending" then I get the requester:

-----------
There was an error with the returned data.
Please try again or check your network.
-----------

If I search for the name of a station that I know was present,
it no longer finds it.

Probably some server "improvement" somewhere....

Thanks,

PJS

@logout

Na Zdravi!

Welcome to our little corner of the net! I hope you really
enjoy your experience with the new SAM460.

Yes, AmigaOS is quite different from other OS's, but it's also
very straightforward. A file is a file; a program; a program;
and you can actually understand all the pieces of the OS.

Being a small corner of the computing world with no big corporate
parents, we also have to do so many things ourselves. Our own apps,
tools and methods. That can be frustrating, especially if someone comes
from a spoonfed world.

But most have us appreciate, enjoy (are addicted to) the feel and
pleasure of using the Amiga. I hope you find it too.

Let us know what questions you've got and where us users can help.

Enjoy!

PJS

Hey guys,

FWIW, we had an HP LaserJet 4 -- a tank -- that worked great (*)
with the Amiga LPR driver for decades.

(*) = don't print too many pages at once. No bufferring in the
LPR driver.

When it eventually died, I found that several HP printers would
still print from the Amiga if I just changed the HP LJ4 output
to the new printer's IP address.

Granted it also seems that HP - while they claim to support
Postscript, LIES - if you send a straight postscipt file in
color or other than "letter" size (8x11), it ignores all that.

But at least it gives you basic printing most of the time.

Yes, we need at least some part of CUPS..... Hopefully without
Weasel Oil on it (that just gums up printers and kills Amigas).

Thanks & Good luck,

PJS

@davec555

The thread is coming up with good suggestions...

Any chance bad weather mighta zapped something? It could be
your gfx card, for example. It happened to my XE.

Once you've confirmed the motherboard is getting power to it
(LEDs as mentioned), then I'd suggest pulling all the cards
and seeing if it makes any more booting motions.

If so, plug in one card at a time (start with the gfx card)
and see how things change.

Obviously, changing the PSU is an option.

Please let us know how things go.

GOOD LUCK!

PJS

sheesh... Dupe post...

Bummer!

Have you tried replacing the battery too? It seems like most
all of the NG systems are sensitive to the battery being up to
snuff.

Otherwise, I'd suggest hooking up a serial cable and watching the output if you can. If you're lucky, that will tell you where
it might be failing.

Let us know what you find!

Thanks,

PJS

@elfpipe

You're having problems with your Amiga drives?

It seems like viruses on the Amiga, let alone OS4, are an unlikely
rarity these days (Thankfully).

But maybe you have a drive going bad?

If you're on one of the NG machines with a complete IDE/SATA
driver, you could run smartctl on your drives to see what it
tells you about its health:

smartctl -A [device]:[unit #]

example:

smartctl -A sii3114ide.device:0

Good luck & make a lot of backups! ;D

PJS

@elfpipe

Congratualtions!!

I can just guess at how steep a mountain it is you're climbing.
Thank you very much for your efforts.

It's like you're making it look easy!

;D

PJS

@walkero

It's great to read of your progress! Thanks walkero, rjd324,
afxgroup, jacadcaps and everyone working on the project.

Great little bit of holiday news.

:D

PJS

@Orgin

That's fantastic news!

Good luck with the legal issues. There's lawyers in that
swamp. Beware.

;)

PJS

@white

I have no idea what you're trying to accomplish. ...and why
you just don't use YT.rexx. Are you trying to do something
more than playing videos???

I can just type this in the CLI:

<path>/YT.rexx <YT URL> autoplay

I get an MPlayer or FFplay window (as needed) and it just plays.
No fuss, no muss.

No clue about your videos (I guess).... How about posting
them something somewhere Amiga-Friendly?

Good luck,

PJS

@white

OK, now you seem to be talking about viewing videos... Not
sending out videos from a camera. hmmm...

Just install/configure YT.rexx, MPlayer and FFPlay *correctly*
and then run YT.rexx (either in shell or from most any Amiga
browser) and stream the video in MPlayer or FFPlay, as needed.

I think you need to clarify your understanding of what those
programs do... YT.rexx just decodes/decyphers the YT stream
URLs and MPLayer and FFPlay just stream/play the found streams.
No "conversion" is taking place, pre se.

Playing vids on peecee??? You're on your own.

Playing videos within an Amiga browser? AFAIK, Oddity has
occasionally been able to do it, but reliably or for any length
of time? Way more overhead and trouble than playing directly
in a video player, IMHO. Get the right tool for the job! ;)

Tip: Goggles "improved" YouTube again, so I think you have to
spoof in Oddity as an iPad (IIRC) to see anything.

Good luck,

PJS

@white

I'm not sure what you're trying to do and what direct connection
it has to Timberworlf....

If you want to remotely view a local IP camera, if it provides
a simple connection (like in your video), you should just be
able to connect to the IP address & port # with MPLayer or
FFPlay and view away. I do with a number of cameras/apps at
home/work with my Amigas.

Of course there's the complexity of getting through your router
to provide access from the WAN (aka Internet). Each router is
different and you'll need some way to find your LAN's internet
IP address. That can be challenging!

To simplify that a bit, you should look into dynamic domain name
services. http://www.ddns.net is an example.

Good luck,

PJS

Hi guys,

I didn't think Timberwolf ever stopped working (at least from
a clean start **)... It's just that it has lost any ability to
do contemporary secure connections (https://, etc).

(**) FWIW, I did find that for TW to run somewhat reliably, you
should delete all the user "profile" stuff. So I added these
line to the start of the TW CLI startup script:

if exists CurrentUserProfile NOREQ
requestchoice "Timberworlf starting..." "Deleting old*nsession files." "Proceed"
delete CurrentUserProfile/#? all force
endif

I wonder how well TW would work if the new SSL code could be
compiled into the existing source.

Good luck,

PJS

@Nielse

Interesting, walkero's spacebar trick seems to be working as described here... Great trick.

FWIW, I'm running Find v53.15. Any chance it's a version specific thing?

Maybe you need to be sure not to have MattyOS polluting your SYS:? ;D

PJS