RoboCopy XP026 Return Code

  • Thread starter Thread starter Alain
  • Start date Start date
A

Alain

With RoboCopy version XP026 the Return Code is always 0 (even with a fatal
error) instead of what it should be according to the documentation. Is
anyone know a workaround to this problem or if there is an update that fix
it?

I was also wondering why the version XP026 is 3 times bigger than XP010 for
the only few extra features, was there major flaws to address in version
XP010? Is there any features and flaws comparaison table of the different
versions?

Thanks!
 
This seems to be the first result that comes up when you search for robocopy xp026 return code, so I'm going to post this here... I needed to run robocopy on a 2003 server, so I couldn't use the newer version. My only options were xp010 and xp026. But I needed unicode support, and I also needed it to return a valid error code. So, I decided I would figure out why xp026 didn't return a valid error code. I ran it through IDA and traced until I found the offending line of code and noop'ed it. Problem solved.

It's 2012 now, so I doubt many people are still on Server 2003, and the newer versions of robocopy fix the problem anyway. But just in case there's someone out there like me that has this exact problem and doesn't mind altering an exe, here's what to do:
Open the xp026 version (make sure it's the right one) of the robocopy exe in a hex editor.
Search for "8B C6 8B 4D F4 5F 5E 33 C0"
Change the last two pairs ("33 C0") to "90 90". So it should end up looking like "8B C6 8B 4D F4 5F 5E 90 90"
And save.

Warning: Do this at your own risk. Be aware you're probably breaking a eula, I didn't read it. Good luck!

-Ken
 
Hey if you can have a changed c:\windows and then symbolic link say C:\windblows to c:\windows then run a ext2 IFS sytem form is / then c:\windows could make /winblows/ c:\windows for the sake of block symlink for fortifieing a notable drive as a windows partition the hard link to drive mountvol on ext2 IFS in /winblows/ what force happens is appending hdd1 partition 2 and then backup on hdd1 partition 1 then when change partition 1 to 2 is framset to quickly antivirus test that imediate change live hard ware dismount backup clone and change set file sighting is remanded into system clone for benifiting chance of checked viral alert quarentine will then replace file from on c:\windows thus lending drive hdd2 then cloning the hdd1 to hdd2 file at one time registering the c:\windows fully usefull and unchanged for purpose of file tampering virus trojens and malware never tampering and letting windows blow its file make-up to the point of no return
as seen so vivid on boot you could then make vitrual vmdk to then act as a backup hdd1 of which then saves the virus quarenteened file original viral free code and replaces the viral code with original viral free

most quarenteens cannot cleant the files needed that windows relies on at boot so file miss leads the file and bluescreens the adjacent and every boot including safe mod is apparently blue screen death thus dead windows partition reinstall...

not all of us have cdrom dvd drives or backup thumbs of our windows due to netbooks being drive less and suffer in boots no windows disk come with netbook shiet

please tell me if i can change and how to change / rename c:/windows
most needed to netbook lockdown

hey windows 7 with xp mode will do what is about to make above possible.

but need code to rename c:\windows
within windows 7 xp moded

hey if it works i will baffle the tech world....hehe lol

otherwise back to dos baby!!!!!!!!!!

multi boot dos probably till reply
 
Back
Top