I'm using Mac OS X, with Parallels build 5.0.9376 - running Windows XP v5.1 with sp3.
I've updated .NET to 3.5 manually and done all required updates through Windows update. I also tried updating the X360 DLL file suggested previously. Still, no joy. When launching WT# it gives me the message: "WillowTree has encountered a problem and needs to close."
I am at a loss as to why it won't open other than I'm running a virtual machine, but I haven't had this problem in the past as most things run smoothly (well, as smoothly as can be expected) via the parallel boot.
Help?
Thanks in advance.
BC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the program is actually crashing with the "WillowTree has encountered a problem and needs to close message", then there should be an entry in the Windows application event log. That may help to figure out the nature of the problem.
Run WillowTree# and let it crash. Click Start->Run in the Windows start menu and type "eventvwr" in the box and hit enter. When the event viewer opens up, click on "Application" in the list on the left. There should be an entry near the top (probably the first one) that says Error for type. Double-click it and there should be an up and down arrow on the right side of the window and below it is a copy icon (it looks like two sheets of paper). Click that to copy the error information to the clipboard then paste it here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm, looks like that the .NET is still my problem? Apparently I didn't update correctly. Am I seeing that correctly?
Also, I have to say, you are on your game Matt911. I've been scouring the boards here looking for answers and you are quick and responsive. Always awesome to see such support with this kind of application.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't tell you by looking at this if it is a NET version problem just from this error. It says NET Runtime 2.0, but that doesn't definitively tell you what version of NET you are using because NET 3.5 is actually built as an extension on top of NET 2.0. A lot of errors in NET 3.5 will give reports that say NET runtime 2.0.
What I was more interested in seeing is what kind of error it says it is having. It says the error is a URI format exception. I think that means WT has encountered a badly formatted internet URL. I can't tell you why that would happen since I've never seen it happen before. Could be a corrupt NET framework installation, corrupt WT binary, or maybe some exotic bug with the mac virtual machine software. I think the URLs are hard-coded so if they didn't work for one person they shouldn't work for anyone. Maybe there's a way to work around this issue even though I can't tell you what is causing it.
There are two places that I know of that WillowTree tries to access the internet where it would be using a URL. One is during the WillowTree update check when you start the program. This would occur whether or not you open any savegame file right after you start the program. The other occurs when you try to load an Xbox 360 savegame because the X360 library has a version check of its own.
I made an experimental version of WillowTree# 2.2.1 without the WT update check a number of months back to use for diagnostic purposes to try to resolve a crash some people were getting which ultimately turned out to be related to an error in the 1.0.0.27 version of the X360 library. It didn't solve that problem since it only removed the WT web check which worked fine, not the X360 library one that was causing the crash. It does however remove the first instance of internet access that I was mentioning above so it might bypass the error. You can find a copy of it in my personal download area located here:
At that time I also made a modified version of the X360 library that circumvents its internet check, but I wasn't sure it would work right so instead of releasing a binary I just recommended that people download the updated version which does not crash from that error anymore from the author's website. I made another modification to it and released a compiled a binary to resolve the tiger icon bug recently. You can find it in the official file area here:
If you install the no update version of WT above and use the X360 library above with it then WillowTree should not access the internet at all and maybe you can circumvent this problem. Try it and see what happens. Let me know what the result is.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Crashed at launch again. This is the error report. I tried it without the updated xbox library and then with, and both attempts yielded the same outcome: crash at launch. Sorry… Perhaps I'm just not meant to mod Borderlands. ;)
Hmm I'm not sure where else the code would use a URI other than those internet update checks. Perhaps in the XML parser which might use them for paths because XML is closely related to internet technologies.
Please make sure you have NET Framework 3.5 service pack 1 installed. To do so click Start->Run, type in "regedit" and hit enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5. In the window on the right side the value for "Install" and "SP" should be 0x00000001 (1). The value I have for "Version" is 3.5.30729.01. If you have the same values then NET Framework 3.5 service pack 1 is installed and fully up-to-date.
If that's not the problem I'm afraid I am out of ideas. You would have to install Visual Studio C# Express 2010 and compile the source code yourself then run it in debug mode to get any more detailed information about exactly which invalid string or operation is causing the crash and whether it is an error in WT or in the other software on your machine. That's not a task that your average non-programmer would be up to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That all matches. Must be something in the dual boot program Parallels that's causing the issue. Oh well, I didn't really need that much backpack space anyways. Thanks so much for the help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had the same exact issue, even after I *thought* I'd installed NET Framework 3.5 SP1.
I re-downloaded the install package from Microsoft (saving the entire ~220MB thing locally, instead of the 2.8MB web installer) and had it "repair" my NET installation… then I restarted my virtual machine, and… voila! It works perfectly now.
However, the issue I'm currently facing is that I can't seem to get it to recognize my modded save games… no matter what I do it keeps displaying my saved games from before I started modding, and I this is probably a non-WT# issue
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Take a look at my project for Mac: https://sourceforge.net/projects/mactree/
Please test if it works for you, I have only tested it on my PS3 saves.
I'm still working on it let me know if it does't work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
intyre, it works for me, sort of. It can tell what character a certain save is, but nothing else. No level, no experience, no nothing. Can't see completed quests, items, anything like that. I'd really appreciate it if you could keep working on it, seeing as I'm having the same problem as those above me with WillowTree throwing a fit over being run in Parallels.
I'm running the Mac version of Borderlands, for the record.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using Mac OS X, with Parallels build 5.0.9376 - running Windows XP v5.1 with sp3.
I've updated .NET to 3.5 manually and done all required updates through Windows update. I also tried updating the X360 DLL file suggested previously. Still, no joy. When launching WT# it gives me the message: "WillowTree has encountered a problem and needs to close."
I am at a loss as to why it won't open other than I'm running a virtual machine, but I haven't had this problem in the past as most things run smoothly (well, as smoothly as can be expected) via the parallel boot.
Help?
Thanks in advance.
BC
If the program is actually crashing with the "WillowTree has encountered a problem and needs to close message", then there should be an entry in the Windows application event log. That may help to figure out the nature of the problem.
Run WillowTree# and let it crash. Click Start->Run in the Windows start menu and type "eventvwr" in the box and hit enter. When the event viewer opens up, click on "Application" in the list on the left. There should be an entry near the top (probably the first one) that says Error for type. Double-click it and there should be an up and down arrow on the right side of the window and below it is a copy icon (it looks like two sheets of paper). Click that to copy the error information to the clipboard then paste it here.
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 8/22/2011
Time: 09:05:17
User: N/A
Computer: BRADCLARK740F
Description:
EventType clr20r3, P1 willowtree#.exe, P2 2.2.1.0, P3 4d6c17b7, P4 system, P5 2.0.0.0, P6 4db9c770, P7 1b38, P8 75, P9 system.uriformatexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 77 00 69 00 6c 00 .w.i.l.
0018: 6c 00 6f 00 77 00 74 00 l.o.w.t.
0020: 72 00 65 00 65 00 23 00 r.e.e.#.
0028: 2e 00 65 00 78 00 65 00 ..e.x.e.
0030: 2c 00 20 00 32 00 2e 00 ,. .2…
0038: 32 00 2e 00 31 00 2e 00 2…1…
0040: 30 00 2c 00 20 00 34 00 0.,. .4.
0048: 64 00 36 00 63 00 31 00 d.6.c.1.
0050: 37 00 62 00 37 00 2c 00 7.b.7.,.
0058: 20 00 73 00 79 00 73 00 .s.y.s.
0060: 74 00 65 00 6d 00 2c 00 t.e.m.,.
0068: 20 00 32 00 2e 00 30 00 .2…0.
0070: 2e 00 30 00 2e 00 30 00 ..0…0.
0078: 2c 00 20 00 34 00 64 00 ,. .4.d.
0080: 62 00 39 00 63 00 37 00 b.9.c.7.
0088: 37 00 30 00 2c 00 20 00 7.0.,. .
0090: 31 00 62 00 33 00 38 00 1.b.3.8.
0098: 2c 00 20 00 37 00 35 00 ,. .7.5.
00a0: 2c 00 20 00 73 00 79 00 ,. .s.y.
00a8: 73 00 74 00 65 00 6d 00 s.t.e.m.
00b0: 2e 00 75 00 72 00 69 00 ..u.r.i.
00b8: 66 00 6f 00 72 00 6d 00 f.o.r.m.
00c0: 61 00 74 00 65 00 78 00 a.t.e.x.
00c8: 63 00 65 00 70 00 74 00 c.e.p.t.
00d0: 69 00 6f 00 6e 00 20 00 i.o.n. .
00d8: 4e 00 49 00 4c 00 0d 00 N.I.L…
00e0: 0a 00 ..
Hmm, looks like that the .NET is still my problem? Apparently I didn't update correctly. Am I seeing that correctly?
Also, I have to say, you are on your game Matt911. I've been scouring the boards here looking for answers and you are quick and responsive. Always awesome to see such support with this kind of application.
I can't tell you by looking at this if it is a NET version problem just from this error. It says NET Runtime 2.0, but that doesn't definitively tell you what version of NET you are using because NET 3.5 is actually built as an extension on top of NET 2.0. A lot of errors in NET 3.5 will give reports that say NET runtime 2.0.
What I was more interested in seeing is what kind of error it says it is having. It says the error is a URI format exception. I think that means WT has encountered a badly formatted internet URL. I can't tell you why that would happen since I've never seen it happen before. Could be a corrupt NET framework installation, corrupt WT binary, or maybe some exotic bug with the mac virtual machine software. I think the URLs are hard-coded so if they didn't work for one person they shouldn't work for anyone. Maybe there's a way to work around this issue even though I can't tell you what is causing it.
There are two places that I know of that WillowTree tries to access the internet where it would be using a URL. One is during the WillowTree update check when you start the program. This would occur whether or not you open any savegame file right after you start the program. The other occurs when you try to load an Xbox 360 savegame because the X360 library has a version check of its own.
I made an experimental version of WillowTree# 2.2.1 without the WT update check a number of months back to use for diagnostic purposes to try to resolve a crash some people were getting which ultimately turned out to be related to an error in the 1.0.0.27 version of the X360 library. It didn't solve that problem since it only removed the WT web check which worked fine, not the X360 library one that was causing the crash. It does however remove the first instance of internet access that I was mentioning above so it might bypass the error. You can find a copy of it in my personal download area located here:
http://sourceforge.net/projects/matt911.u/files/
At that time I also made a modified version of the X360 library that circumvents its internet check, but I wasn't sure it would work right so instead of releasing a binary I just recommended that people download the updated version which does not crash from that error anymore from the author's website. I made another modification to it and released a compiled a binary to resolve the tiger icon bug recently. You can find it in the official file area here:
http://sourceforge.net/projects/willowtree/files/x360lib/
If you install the no update version of WT above and use the X360 library above with it then WillowTree should not access the internet at all and maybe you can circumvent this problem. Try it and see what happens. Let me know what the result is.
Crashed at launch again. This is the error report. I tried it without the updated xbox library and then with, and both attempts yielded the same outcome: crash at launch. Sorry… Perhaps I'm just not meant to mod Borderlands. ;)
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 8/22/2011
Time: 16:44:29
User: N/A
Computer: BRADCLARK740F
Description:
EventType clr20r3, P1 willowtree#.exe, P2 2.2.1.0, P3 4d672314, P4 system, P5 2.0.0.0, P6 4db9c770, P7 1b38, P8 75, P9 system.uriformatexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 77 00 69 00 6c 00 .w.i.l.
0018: 6c 00 6f 00 77 00 74 00 l.o.w.t.
0020: 72 00 65 00 65 00 23 00 r.e.e.#.
0028: 2e 00 65 00 78 00 65 00 ..e.x.e.
0030: 2c 00 20 00 32 00 2e 00 ,. .2…
0038: 32 00 2e 00 31 00 2e 00 2…1…
0040: 30 00 2c 00 20 00 34 00 0.,. .4.
0048: 64 00 36 00 37 00 32 00 d.6.7.2.
0050: 33 00 31 00 34 00 2c 00 3.1.4.,.
0058: 20 00 73 00 79 00 73 00 .s.y.s.
0060: 74 00 65 00 6d 00 2c 00 t.e.m.,.
0068: 20 00 32 00 2e 00 30 00 .2…0.
0070: 2e 00 30 00 2e 00 30 00 ..0…0.
0078: 2c 00 20 00 34 00 64 00 ,. .4.d.
0080: 62 00 39 00 63 00 37 00 b.9.c.7.
0088: 37 00 30 00 2c 00 20 00 7.0.,. .
0090: 31 00 62 00 33 00 38 00 1.b.3.8.
0098: 2c 00 20 00 37 00 35 00 ,. .7.5.
00a0: 2c 00 20 00 73 00 79 00 ,. .s.y.
00a8: 73 00 74 00 65 00 6d 00 s.t.e.m.
00b0: 2e 00 75 00 72 00 69 00 ..u.r.i.
00b8: 66 00 6f 00 72 00 6d 00 f.o.r.m.
00c0: 61 00 74 00 65 00 78 00 a.t.e.x.
00c8: 63 00 65 00 70 00 74 00 c.e.p.t.
00d0: 69 00 6f 00 6e 00 20 00 i.o.n. .
00d8: 4e 00 49 00 4c 00 0d 00 N.I.L…
00e0: 0a 00 ..
Hmm I'm not sure where else the code would use a URI other than those internet update checks. Perhaps in the XML parser which might use them for paths because XML is closely related to internet technologies.
Please make sure you have NET Framework 3.5 service pack 1 installed. To do so click Start->Run, type in "regedit" and hit enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5. In the window on the right side the value for "Install" and "SP" should be 0x00000001 (1). The value I have for "Version" is 3.5.30729.01. If you have the same values then NET Framework 3.5 service pack 1 is installed and fully up-to-date.
If that's not the problem I'm afraid I am out of ideas. You would have to install Visual Studio C# Express 2010 and compile the source code yourself then run it in debug mode to get any more detailed information about exactly which invalid string or operation is causing the crash and whether it is an error in WT or in the other software on your machine. That's not a task that your average non-programmer would be up to.
That all matches. Must be something in the dual boot program Parallels that's causing the issue. Oh well, I didn't really need that much backpack space anyways. Thanks so much for the help!
I had the same exact issue, even after I *thought* I'd installed NET Framework 3.5 SP1.
I re-downloaded the install package from Microsoft (saving the entire ~220MB thing locally, instead of the 2.8MB web installer) and had it "repair" my NET installation… then I restarted my virtual machine, and… voila! It works perfectly now.
However, the issue I'm currently facing is that I can't seem to get it to recognize my modded save games… no matter what I do it keeps displaying my saved games from before I started modding, and I this is probably a non-WT# issue
For the record, I'm running VWware Fusion (v3.0) on OS X Lion with Windows XP Pro SP3.
I used WillowTree#-2.2.1.102, although earlier versions also work perfectly after repairing the .NET install
Hi guys
Take a look at my project for Mac: https://sourceforge.net/projects/mactree/
Please test if it works for you, I have only tested it on my PS3 saves.
I'm still working on it let me know if it does't work.
intyre, it works for me, sort of. It can tell what character a certain save is, but nothing else. No level, no experience, no nothing. Can't see completed quests, items, anything like that. I'd really appreciate it if you could keep working on it, seeing as I'm having the same problem as those above me with WillowTree throwing a fit over being run in Parallels.
I'm running the Mac version of Borderlands, for the record.