Calling all real hardware testers
Moderator: Moderator Team
Calling all real hardware testers
Would anyone like to join in doing a little testing?
My main test computer's hard drive is partitioned C: D: E: and F:
C: D: E: I use for Ros and F: is used to store puppy files.
I have down-loaded Gramps from Sourceforge (http://gramps-project.org/download/).
The unzipped files are on drive E: in a folder called 'gramps'.
I have in Ros, tried to copy this folder from drive E: to drive C:, but after at least 20 minutes I gave up. The drive light was now very intermittent, the mouse was moveable, but nothing else worked, so I hit the reset button.
On reboot, the gramps folder is there in drive C:, but when I use the properties menu on the folder, I find that it is only half copied.
Here are some images of the folder properties before and after,
in puppy linux
[ external image ]
and Ros.
[ external image ]
Notice the different files sizes in Ros and Puppy. It looks like Ros still does not report true file size!
So if you have more than one partition on your test computer(s) hard drive and you want to help, then you are more than welcome to do so.
Things also to look for, are; the source drive folder contents, are they visible after the copy attempt; can you delete the source folder after the copy attempt.
This is not official, I just want someone else to confirm my findings or show that it is a fault with my computer.
My main test computer's hard drive is partitioned C: D: E: and F:
C: D: E: I use for Ros and F: is used to store puppy files.
I have down-loaded Gramps from Sourceforge (http://gramps-project.org/download/).
The unzipped files are on drive E: in a folder called 'gramps'.
I have in Ros, tried to copy this folder from drive E: to drive C:, but after at least 20 minutes I gave up. The drive light was now very intermittent, the mouse was moveable, but nothing else worked, so I hit the reset button.
On reboot, the gramps folder is there in drive C:, but when I use the properties menu on the folder, I find that it is only half copied.
Here are some images of the folder properties before and after,
in puppy linux
[ external image ]
and Ros.
[ external image ]
Notice the different files sizes in Ros and Puppy. It looks like Ros still does not report true file size!
So if you have more than one partition on your test computer(s) hard drive and you want to help, then you are more than welcome to do so.
Things also to look for, are; the source drive folder contents, are they visible after the copy attempt; can you delete the source folder after the copy attempt.
This is not official, I just want someone else to confirm my findings or show that it is a fault with my computer.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
There's a few things going on here, two of which I'm actually working on at the moment.
Copy and paste through explorer is not multi threaded and works on the foreground thread. This makes it block interactions with explorer which is really annoying (but I'm reworking this completely). The second thing is that the file operations dialog is not fully implemented, so feedback on copying is not available (working on it). And lastly... it's just slow.
I think you just needed to wait longer.
Copy and paste through explorer is not multi threaded and works on the foreground thread. This makes it block interactions with explorer which is really annoying (but I'm reworking this completely). The second thing is that the file operations dialog is not fully implemented, so feedback on copying is not available (working on it). And lastly... it's just slow.
I think you just needed to wait longer.
Re: Calling all real hardware testers
Ok, thanks for the feed-back.Post by Frontier » 20 Dec 2013 12:00
I think you just needed to wait longer.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
You can also copy with the command line.
Re: Calling all real hardware testers
It didn't work for me. See image below:Frontier wrote:You can also copy with the command line.
[ external image ]
Or should I have inserted 'to' as in 'copy E:\gramps to C:\gramps; but it reports 1 file copied (there should have many files copied).
There are similar problems with delete!
Last edited by oldman on Sun Dec 22, 2013 12:03 pm, edited 1 time in total.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
Use
Yes, I'm aware that the delete operation has the same problem. Windows has a function called DeleteItemsThreadProc called by SHCreateThread to push deletiong to a background thread. We don't have this yet and it's handled in the context menu, which is a bit of an ugly cludge. Once I get copying working properly, I'll do delete too.
The /E means recurse through sub directories.xcopy /E E:\gramps C:\gramps
Yes, I'm aware that the delete operation has the same problem. Windows has a function called DeleteItemsThreadProc called by SHCreateThread to push deletiong to a background thread. We don't have this yet and it's handled in the context menu, which is a bit of an ugly cludge. Once I get copying working properly, I'll do delete too.
Re: Calling all real hardware testers
With regards to the directory sizes being different, you probably hit reset in the middle of a file copy, which would leave the directory in a less than consistent state. Combined with our not so excellent FAT driver... you'll get problems with which files it sees.
Re: Calling all real hardware testers
I have tried the above with success, but also with some anomalies.by Frontier » 22 Dec 2013 03:59
Use
xcopy /E E:\gramps C:\gramps
The /E means recurse through sub directories.
[ external image ]
I think the "Is 's' a file name or a directory" in the above image, should read "Is 'gramps' a file name or a directory".
I typed D and the copy started and ran normally. It took 34 minutes approximately,
[ external image ]
But it gave d instead of the number of files copied.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
"s" and "d"? It seems to me that either LoadStringW or GetModuleHandleW is ignoring the "%" symbol.oldman wrote:I have tried the above with success, but also with some anomalies.by Frontier » 22 Dec 2013 03:59
Use
xcopy /E E:\gramps C:\gramps
The /E means recurse through sub directories.
[ external image ]
I think the "Is 's' a file name or a directory" in the above image, should read "Is 'gramps' a file name or a directory".
I typed D and the copy started and ran normally. It took 34 minutes approximately,
[ external image ]
But it gave d instead of the number of files copied.
Re: Calling all real hardware testers
Well I'm glad you had some success oldman. I'm currently testing my threaded copy code, which should make things easier in future.
With regards to the wrong characters in xcopy, best bet is to check jira.reactos.org to see if that bug has been reporred and file one if it hasn't.
With regards to the wrong characters in xcopy, best bet is to check jira.reactos.org to see if that bug has been reporred and file one if it hasn't.
Re: Calling all real hardware testers
I have checked jira for this bug, and did not find anything related, so I have made a bug report here: https://jira.reactos.org/browse/CORE-7720Frontier wrote:Well I'm glad you had some success oldman. I'm currently testing my threaded copy code, which should make things easier in future.
With regards to the wrong characters in xcopy, best bet is to check jira.reactos.org to see if that bug has been reporred and file one if it hasn't.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
Just an update for those interested.
Below is a screenshot, which shows both Ros xcopy and Windows xcopy running in WindowsXP.
[ external image ]
No prizes for guessing which is which!
Below is a screenshot, which shows both Ros xcopy and Windows xcopy running in WindowsXP.
[ external image ]
No prizes for guessing which is which!
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: Calling all real hardware testers
I think the upper one is the ROS one, because it reports "d files copied".
Re: Calling all real hardware testers
Correct.gonzoMD » 24 Dec 2013 09:40
I think the upper one is the ROS one, because it reports "d files copied".
Fixed
So, thanks go to akhaldiby akhaldi
[XCOPY]
* Fix the resources that reference parameters.
CORE-7720 #resolve #comment Fixed in r61366. Thanks !
We now await Frontier's efforts, then copy (cut and paste maybe too) will be totally fixed.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Who is online
Users browsing this forum: DotBot [Crawler], Google [Bot], Semrush [Bot] and 1 guest