Advertisement
Guest User

Untitled

a guest
May 21st, 2017
518
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.54 KB | None | 0 0
  1. Conversation with hectorofchad on 1/27/2010 5:11:18 PM:
  2. (5:11:18 PM) hectorofchad:
  3. Someone should also designate a new patching format because UPS is clunky for something so revolutionary.
  4.  
  5. Zahlman and Hextator to the rescue~
  6.  
  7. (Or just Hextator if Zahlman acts like he has more important things to do (he doesn't))
  8. (5:11:35 PM) zahlman@gmail.com:
  9. "something so revolutionary"?
  10. (5:11:44 PM) hectorofchad:
  11. the original thread that it was posted in
  12. (5:11:51 PM) hectorofchad:
  13. had everyone going "omg this is way better" and shit
  14. (5:11:56 PM) hectorofchad:
  15. of course that was in like 2001
  16. (5:12:00 PM) hectorofchad:
  17. but it was a big deal then
  18. (5:12:13 PM) hectorofchad:
  19. and then for some reason we were so blinded by all that glory that we didn't notice it has terrible flaws
  20. (5:12:25 PM) hectorofchad:
  21. ever notice how much more sensible it is to stack IPS patches than UPS patches
  22. (5:12:29 PM) zahlman@gmail.com:
  23. you could make it like... basically a script for a command-line FEditor
  24. (5:12:46 PM) hectorofchad:
  25. UPS patches force you to disable checksum checking if you're using more than one
  26. (5:12:49 PM) hectorofchad:
  27. that's Bad
  28. (5:12:51 PM) zahlman@gmail.com:
  29. yeah
  30. (5:13:00 PM) zahlman@gmail.com:
  31. in a lot of cases patches just don't stack regardless though
  32. (5:13:01 PM) hectorofchad:
  33. basically my spec is just
  34. (5:13:04 PM) hectorofchad:
  35. "UPS
  36. (5:13:13 PM) hectorofchad:
  37. with the checksum applied to sections instead of the entire file"
  38. (5:13:37 PM) hectorofchad:
  39. or hell
  40. (5:13:40 PM) hectorofchad:
  41. a single checksum
  42. (5:13:45 PM) hectorofchad:
  43. but for only the relevant bytes
  44. (5:13:54 PM) hectorofchad:
  45. this way
  46. (5:13:57 PM) hectorofchad:
  47. you can stack the patches
  48. (5:14:01 PM) hectorofchad:
  49. and still undo them
  50. (5:14:10 PM) hectorofchad:
  51. as well as check if they conflict
  52. (5:15:12 PM) zahlman@gmail.com:
  53. hmm
  54. (5:15:23 PM) hectorofchad:
  55. and of course
  56. (5:15:31 PM) hectorofchad:
  57. it would be able to patch files that are over 16 megabytes
  58. (5:15:33 PM) hectorofchad:
  59. as usual
  60. (5:15:47 PM) hectorofchad:
  61. if we wanted, we could be cocky/stupid
  62. (5:15:54 PM) hectorofchad:
  63. and store addresses as variable length ints
  64. (5:16:02 PM) hectorofchad:
  65. then it'd be future proof!
  66. (5:17:45 PM) hectorofchad:
  67. and we could provide provisions for extendability for things like patch file encryption and compression and anything else we can think of pertaining to mangling the data
  68. (5:17:55 PM) zahlman@gmail.com:
  69. hmm.
  70. (6:04:17 PM) hectorofchad:
  71. let me know if you have any outstanding ideas on the matter
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement