Menu

could not open save

Help
jto
2013-06-29
2013-06-30
  • jto

    jto - 2013-06-29

    Hello folks,

    I have looked at this forum and others before posting and haven't found an answer so far, so here goes.

    I cannot open a save file for PS3. I have tried renaming the sav file as "Save001" instead of "SAVE001" and made sure to play until the fixer upper part of the game. So far, I have no luck.

    I have included a link to a screen capture of the "Open" function on WT in case that helps. It's version WT#2.2.1NoUpdate. Borderlands is a rental and I updated the version as soon as it came up. I don't think that there are any DLC on it.

    I think my problem is that I cannot keep the PS3 folder and subsequent files as not "read only." Each time I go to properties and uncheck read only, once I exit out of the folder and go back to check it, it is read only again. That is frustrating.

    Any help would be awesome. Thanks!

     

    Last edit: jto 2013-06-29
  • matt911

    matt911 - 2013-06-29

    Make sure you have extracted WillowTree# into a folder that you have read and write access to. Every user should have read and write access to their desktop and subfolders of My Documents, but normal users don't have write access to subfolders of Program Files. WT# needs to read and write data files and temporary files, so you can't just run WillowTree# from inside the zip file.

    As far as I know the USB flash drive should not be read only. I would copy the file from the flash drive to my computer, then edit it on my computer, then copy it back to the flash drive. Make sure you are getting the savegame from the USB flash drive, not trying to read the hard drive of the PS3 (which I think is encrypted) directly.

    If you have difficulty I'd suggest looking for a video tutorial at http://www.youtube.com.

    The experimental version of WillowTree# has more functionality and probably less bugs than the release version at this point. It also has error messages that are more helpful determining what is the problem when something doesn't work. You may download it from the experimental folder in the files area and try that if you still can't figure out why WT# can't load your savegame. It might provide an explanation why.

     

    Last edit: matt911 2013-06-29
    • jto

      jto - 2013-06-29

      I extracted the WT to the Downloads section of my computer, then cut and pasted the whole folder to the desktop. The WT folder is still "read only" with a blue box. The WT program is not read only.

      Once again, the folders containing the PS3 save file are still marked with the blue read only box. The actual file itself is not.

      I'm still not having any luck. I might try the experimental version of WT

       
  • jto

    jto - 2013-06-29

    I tried using WT experimental. When I went to open it, nothing happened. No error message, nothing. I'll continue to try using WT#

     
  • matt911

    matt911 - 2013-06-29

    That's very interesting. I've never heard of that behavior with the experimental version.

    Have you installed NET Framework 3.5 on your machine? WillowTree# requires NET Framework 3.5 Service Pack 1.

    http://www.microsoft.com/en-us/download/details.aspx?id=22

    Note that version 3.5 specifically is required. NET Framework 4.0 or 4.5 will not work. They are different families of the NET Framework product that can both be installed on your computer at the same time.

     

    Last edit: matt911 2013-06-29
  • matt911

    matt911 - 2013-06-29

    I just looked and on my computer if I create a folder on the desktop in Windows 8 then right click it and select properties it has a black box in the read-only box, which means "some of the files contained here are read only" I am guessing. If I click the read only box it will ask me if I want to make all the files read only. I say yes and it updates them and it turns to a check mark which I assume means "all files contained here are read only". If I then uncheck it, it'll ask me if I want to make them all readable. I do that and that makes the checkbox empty, but then if I close it and go back and right click the folder and do properties it has the black box again.

    If this is what you are seeing, it is normal behavior and it does not mean that your folder is read only.

    To see if the folder is read only, right click on it and select Properties, click the Security tab, click on Advanced, click the Effective Access tab, click Select User, type your user name, click View Effective Access. If 'Full Control' is checked then the folder has full read and write access.

     

    Last edit: matt911 2013-06-29
  • jto

    jto - 2013-06-29

    I just tried installing .NET 3.5 on my computer. It got all the way through the install process and crashed. I hate microsoft. I'll try that again...

    What program should my computer try to use to open SAV files? If I have the wrong program seleced (from "Open With") could that have an affect on the file?

     
  • matt911

    matt911 - 2013-06-29

    No it won't have any effect. You must run the WT# executable in the folder then click on the Tree in the upper left corner in the release version (or from the file menu in the experimental) then select open to open a file. You do not drag and drop the file on the WT# executable or associate it with a file extension. It doesn't have command line support for that.

     

    Last edit: matt911 2013-06-29
  • matt911

    matt911 - 2013-06-29

    If you are using Windows 8 or 8.1 here is a page that tells you how to install NET Framework 3.5 that is particular to that version and will not work on Windows 7.

    http://msdn.microsoft.com/en-us/library/hh506443.aspx

     
  • jto

    jto - 2013-06-29

    Thank you for all the replies so far. I was not able to install .NET 3.5 However, I ran a verification utility that stated that 3.5 is functioning properly on my computer (I have 4 installed, using Windows 7). Could this still cause the problem I mentioned?

    Do you know of a way to install 3.5 if I already have 4 installed?

    EDIT-checking the .NET folder I do have some files associated with 3.5 installed...

    Thanks again...

     

    Last edit: jto 2013-06-29
  • matt911

    matt911 - 2013-06-29

    Try this link for some instructions on how to uninstall and reinstall NET Framework in Windows 7.

    http://www.adminarsenal.com/admin-arsenal-blog/bid/75362/How-to-Repair-or-Reinstall-NET-Framework-3-5

    If that doesn't work for you, please tell me exactly what behavior you are seeing when you try to start WillowTree# and/or after you have opened WillowTree# when you try to open the file. Is it crashing, just nothing happening, telling you it can't open the WSG or what exactly is the symptom you are seeing?

    Have you tried to create a new character in Borderlands to make sure that the savegame you are having trouble editing is not corrupted in some way?

     
  • matt911

    matt911 - 2013-06-29

    Also, are you running in any sort of non-standard environment I should be aware of, such as in a virtual machine that could introduce subtle bugs that would not occur on a normal Windows installation?

     
  • jto

    jto - 2013-06-29

    Success! I followed the instructions for turning on and off the 3.5 and it worked. I was previously getting an error message in WT saying "Could not open save" This was with a basic level 7 save on a game I had just created.

    I have been able to open the save and will try modding it when my blood pressure drops back down...

    Thanks for everything

     
  • matt911

    matt911 - 2013-06-29

    Great, sounds like there was some file, registry entry, or configuration associated with NET Framework 3.5 that was corrupted. Windows 7 comes with NET Framework 3.5 SP1, so normally it should not be required to install it on that operating system.

    You might have some instability with your system RAM or a hard drive issue if you have lots of weird random application crashes on your computer. If you do, you should try to visit your motherboard manufacturer's website and check to see if they have a BIOS update availble as that sort of instability is often just bad memory or storage controller timings that are adjusted in a later revision to fix them.

    When you get around to trying to edit your save, note that if you try to modify an item in the WT# you need to click on Save Changes when done editing an existing item or the changes will be discarded as soon as you switch to the next item, then when you are all done editing be sure to use the Save or Save As command from the file menu to actually write it to the storage media.

     

    Last edit: matt911 2013-06-29
  • jto

    jto - 2013-06-30

    Thank you for the last suggestions. I haven't been having any other issues with the laptop.

     

Log in to post a comment.