@leo

Quote:

Yes, this may mean losing compatibility: so what ? I guess it's *high* time the OS gets improved... We won't stay in the past, will we ? The faster compatibilty is dropped, applications taking advantage of it can be written...

Should hardware become available and sales pickup there will then be incentive to develop new software. Until then the system is captive to the past and compatibility cannot be dropped. When will that be? We cannot answer that but hope. I admit to running short on hope for a while.

Noel

@tomazkid

Quote:

Anyway, any errors in NoelFuellers translation?

Thanks - particularly the puzzling stuff where there are italics.

Noel

@Rogue

Thanks for all your hard work and dedication. You have created a great update to the Amiga operating system.

@CodeSmith

It's not bashing, Windows is an old dated operating system. While it has improved over the years the legacy baggage it carries is unloved by millions.

Last edited by DiscreetFX on 21-Aug-2008 at 09:25 PM.
Last edited by DiscreetFX on 21-Aug-2008 at 09:25 PM.

_________________
Sent from my Quantum Computer.

@Rogue

Quote:

Strangely enough, this is exactly the opposite of what you said in your first post.

Sorry for being unclear. What I meant was that it happens rare enough that two tasks share a window that it doesn't matter if it crashes those times.

Quote:

Yes. It's very bold, though, to leave such a choice to a user. How would you know that this will actually be the case or not, without being the developer?

Trial'n'error And the checkmark to enable this behavior should obviously be in the More window.

Besides, don't you think "Ignore DSI" is pretty bold then..? (But please don't remove it!)

Quote:

Actually, no. The task stays in memory. You cannot predict what other task might have resources shared with this one, and removing it would be a danger. As I said before, when a program has crashed, the only sensible way to proceed is to save all work and reboot.

It stays in memory?! What does Kill actually do then?? And why does it cause a crash or system freeze so often, compared to just leaving the GR open and not do anything?

Sure a reboot is the only safe way out, but development would be *very* slow if one couldn't kill off crashed tasks without a reboot every time before trying a new compile...

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Rogue

Quote:

What's wrong with this statement? I recently had installed a program on Windows that came with its own copy protection. From that point on, every time I right-clicked on an icon I get an explorer crash. I don't have the slightest idea why and what to do about it (the proposed fix does not work for me), so I am about to re-install Windows. On the Amiga, I would know where to look. That's what I said, and sadly it is true. This is not about being better or worse. It is about KNOWING your system, about TRANSPARENCY to the user. That's all I said.

Ahhh, there's the rub - you're not exactly a typical Amiga user. I bet a Microsoft employee from the Windows team could have fixed your Windows problem in a few minutes. With me, it's the opposite - when I still used my AmigaOne, I would run programs, things would start misbehaving, and my only recourse would be to reboot because AmigaOS is a complete mystery to me (and unfortunately there's precious little info out there, so things are unlikely to improve any time soon). Transparency is pretty useless when everything is visible but undecypherable. Hyperion really needs to make it a top priority to educate its users. It doesn't even have to take up the time of core developers - your beta testers probably know most of the important stuff, so loosen their NDAs a bit and give them some incentive for writing docs and HOWTOs.

I've used Windows since about two years after CBM died and I've bought quite a few MS Press and O'Reilly books, so I'm usually pretty good at figuring out what to do when something goes wrong with my PC. In your case, it sounds like the program installed a dud shell extension and five minutes with regedit would have fixed your problem.

Quote:

I bet a Microsoft employee from the Windows team could have fixed your Windows problem in a few minutes.

Then why don't they fix Windows itself ?

@elcabron

Tu nombre es ideal, te viene perfecto.

"""
Amiga Arena: What is the objective of your bez with AmigaOS 4.1. where you see as the developer an opportunity for AmigaOS4?

HJF: We want to continue AmigaOS in the embedded area.
There are already interested in favour
AmigaOS 4.1 as the Multimedia Content Platform want to use (for example, a kind of kiosk system).
"""""

This i really cant believe, SAM look in compare to X86 miniitx system, niot very good.
If HJF dont mean SAM in hois statement, who should build a hardware, that can compare with the X86 minitix Systems.

for those who dont know whats for X86 out with intel atom and price look here and compare with SAM.

http://www.mini-tft.de/xtc-neu/index.php/cPath/2539/category/--mini-itx-mainboards.html

http://www.sam440.com/eng/summerfollies.html

Sam need 10-25 Watt but some boards use 5 Watt and are faster clockrate and have 2. level cache.

So i cant believe, that it is posible that OS4+ Hardware go into non OS4 Fan Market

>What's wrong with this statement? I recently had installed a program on Windows >that came with its own copy protection. From that point on, every time I right->clicked on an icon I get an explorer crash. I don't have the slightest idea why and >what to do about it (the proposed fix does not work for me), so I am about to re->install Windows.

thats no good example, copy protection softwares job is to protect from copying, and not easy to find.

And if somebody on AOS write a copy protect to his program he look that his code is not easy find and remove.

and i dont think that amiga coders can write copy protect, code, that work on all OS4 systems with tools etc 100%
problems of copyprotect was also on A500.

Last edited by bernd_afa on 23-Aug-2008 at 08:30 AM.