general question about riscos.

xxx

It’s just a waste of time to try to get serious stuff done here, it’s just about comments on grammar and trying to look smart

I thought you were doing fine¹ and I didn’t see any critique of your grammar apart from the comment from a visiting idiot that we rapidly identified for you.
I did have a bit of a verbal swing at that person who insulted your command of English unjustly. Never been a fan of rude people, and he was.

¹ Apart from a tendency to drop comic art images into a thread for reasons beyond my understanding. I’m not sure whether that stuff is a youth thing that I lost connection with years ago or whether I simply never had it.

xxx

xxx

It’s more the general attitude, like seriously people lieing about things that are supposed to do things, then you need to waste 3 day to figure out that in fact it’s all broken and people who told you this knew it, and then keep saying it does, or find some excuse to say why it doesn’t work,

Example?

to keep bragging how great everything is on riscos that nothing need to be changed or rethought at all, like it already has everything it needs ..

The base problem is that the majority of the user base have programs that work in the OS environment that currently exists but would break if that was substantially changed. Unless someone gifted them with free replacement software or a means of running the old then they wouldn’t take up that version of OS. Note the the replacement would have to have the same user interface behaviour as the old version. Demanding users…

the outdatted infos, the sacarsm and the 100Mo of assembler source it’s clear it seem difficult ..

Yes, it’s difficult. Not least because many of the enthusiasts, like me, don’t have the knowledge to make the required changes. For my part I look at and see if I can clarify bits of documentation by correcting language mistakes, after all if a native English speaker would have difficulty reading the text without reading through several times then how is a non-native supposed to cope?

i can accept that people critics my english

As I said back then, your English is better than many native English people and certainly better than my French. As to the person who did criticise, well as I said earlier, I don’t like rude people.

If riscos is made to stay with basic and assembler and unable to copy a 200ko file without corrupting it then yes not really something for me.

I’ve been copying multi-MB objects for years and I’ve not corrupted one on RISC OS yet. Done the corruption bit many times on Windows.

File corruption seems common on Pi installations with power issues or mismatched SD cards (by mismatched I mean cards whose operating specification is not a good match for the requirements of the Pi SD card slot)

If it has way to do what i want to do, then i’d be glad to hear the brillant syntax to make it so

Sadly, as I mentioned earlier, that won’t come from me. I might know the history of things but that kind of information would need an expert in a field I don’t cover.

If you ask short and specific questions you may prompt a useful answer from one of the few.

xxx

Example?

This.

xxx

You are very unfortunate if you are getting any file corruption. We use RISC OS at work extensively and I think the last time we had a file corruption was about 10 years ago!
Most weeks we copy the whole contents of a customer hard drives to another RISC OS computer using ShareFS or on to a NAS using LanMan98 and back again to a new drive.
Comparing that with Windows where we don’t get corruption but if we select a directory with various sub directories and we try copying that to say a USB drive if it stalls for any reason we have no idea which files have copied and which not (RISC OS copies files in a very ordered way). I can’t believe a modern OS can’t cope with that. I shouldn’t need to use special backup software for a few files in a directory structure, drag and drop should be enough.

Example?

This.

Sorry, I really do not understand that. Perhaps you didn’t understand my question due to its brevity.

I will rephrase / expand:

Could you give an example of an instance where this statement is applicable:

It’s more the general attitude, like seriously people lieing about things that are supposed to do things, then you need to waste 3 day to figure out that in fact it’s all broken and people who told you this knew it, and then keep saying it does, or find some excuse to say why it doesn’t work

because I honestly can’t recall an instance of anyone doing anything that fits the description.

aaa

xxx

xxx

xxx

xxx

xxx

Ok i will give you one example.

I ask how to do something. Then i’m told, ok just do it, it’s free.

Then i say ok, then how about doing it like this ?

nooooooooooo, silly, that’s a mistake, that’s synthax error ..

I believe Steve apologised for the style of his reply. In essence he was trying to point out that you were misunderstanding the capabilities of Basalt. Since he wrote it, I’d call him the expert on the subject.

Ok, so then how i do it ?
I don’t care i just want result just do it.
Ok so let’s do it this way ..
Noooooooo it will break application, it will break everything !! silly that’s a windows thing ..

Ah, I see your frustration. You would like RISC OS to be different than it is currently, and so do we, but people point out that since the result has to cater for old applications the change must be done in a way that doesn’t break those applications¹ or must provide a replacement.
After all, what is the point of an OS that has no applications?

You may have seen the references to making changes without breaking applications in Justin Fletchers RISC OS Rambles.

¹ Hence the interest in the hypervisor concept put up by Jon Abbott as this seeks to remove application and OS revision dependence. In many cases it isn’t the change, or changes, that is impossible rather it is the order of the changes. Dependencies, always the problem in both programming and change in general.
I have just short of £2M of network kit to install in the next 6 months or so. If I could ignore the dependencies it would be no problem and could done and finished in 5 or six weeks. Unfortunately I work at a 24/7 365 establishment.

I t ried to copy a few file on riscos, i’d say not even 20% of them have been copied correctly.

That is strange. While I have never used LanMan (can’t be bothered to set up shares right now), I have copied (via !MTP) from my phone. Possibly to it. Also files from FAT USB stick and also FileCore format USB stick.

A lot of small files, but some biggies too. MP3s, source archive, blah blah. The only problem encountered is a “quirk” in !MTP that replaces Japanese characters with a ‘?’ which also happens to be a valid wildcard so you can probably guess what happens when it tries to create that file. :-)

If I have some time forthcoming, I might set up a share and push some MP3s around (5-12MiB each) to see what happens.

seriously you’re trying to say to me that riscos is a valid replacement and work better that windows ..

When I used to use a networked PC as a “NAS”, and copying videos from an SD card (say, recordings from my PVR) to the NAS, I got into the habit of doing a copy twice instead of a simple move. Why? Because PC to PC seems to have a propensity for creating zero length files (I can see the copy activity bar growing and the hub lights flashing, what does it do with all that data?). It didn’t happen often, maybe once every two or three months – but over a space of years that meant three recordings lost and some more caught before they could be lost as well.
This is XP to XP, local network (100mbit), with an open non-passworded share¹ assigned a drive number in Explorer on the client. Nothing at all unusual.

¹ The host was not connected to the Internet, at all. So open shares were acceptable.

that riscos has no problem of file corruption,

RISC OS can have a file corruption problem on the Pi. If you look at the forums (not here, go Google) you’ll see it is not RISC OS. It is usually either a weak power supply (a meatier PSU cleared up my problems) or a type of SD card that doesn’t agree with the Pi’s hardware. I suspect people using Ultra Mega Super Class 10 cards will be suffering more than people like me using a bog standard class 4 card…

hello we’re in 2015 folks ..

Indeed we are. Summer time as well. Whee! ;-)

You say you are experiencing corruption whilst using a Samba share. That’s a standard Windows style share, right? What version of Windows is performing the sharing? What software are you using on the RISC OS side? Omniclient? With what settings?

xxxx

Dependencies, always the problem in both programming and change in general.

…like all those people who are still tied to ancient versions of MSIE as the stuff that they depend upon won’t run on anything newer.

At work we have a temperature monitoring system that logs temperatures across the site and keeps records of all of this. Well, at a very brief look, the computer looks like it was possibly installed in the mid ‘90s. Given the on-screen ugliness, it may be W95. The interface card looks like it is ISA sized. You don’t find so many computers with ISA inside nowadays. Assuming, of course, the software will even work – if it tries any sort of direct hardware access, the NT class kernel will kill it (that’s XP and anything newer in domestic terms). If it has a custom driver (VxD or whathaveyou), that’s all different for XP as well. And slightly different again for Vista, and no doubt for <insert Windows version> too.

If the thing has been going for so long it is hard to see the screen over the burn-in, then let’s hope it has some more years in it yet! ;-)

xxxx

Not about saying everything works and nothing works at all really that’s just bad mentality ..

There was a very specific reason I was asking you about what you are doing on the RISC OS side. I have an XP box and a Pi. Join the dots.

xxxx

xxx

xxx