ATTENTION! New Body Shop Bug!!!!111!1eleven
BeosBoxBoy:
I have been trying to determine some means for Mac-users to go about solving this issue on their systems. In the absence of a programme that parallels Sims2Pack Clean Installer, it appears that only using Woohoo to open all files with junk-code names for visual inspection is going to work. This is really a miserable solution and I don't know that it will improve for Mac-users.
Mac-users that have Intel-based Macs and have the ability to dual boot into Windows may be able to use Sims2Pack Clean Installer if they can get copies of the downloads folder on to the Windows part of the system; but I wouldn't count on that being easy. Sims2Pack Clean Installer may not work in the absence of registry data for The Sims 2 in Windows - I don't know, I haven't tried.
Debbycus:
*bitches about American working methods, deadlines and wealth-thirst*
Thanks, Yakov, for this... Makes me loath my game and wanna throw rocks over the Atlantic.
I have a question, though. Remembering that I have a small dozen of these strange named files, I opened them up in SimPE, and realized that non of them was anything like the Sims06.package. They were mostly recolours, few of them meshes, and like two were BodyShop items.
What is this?? How did these get into my folder? ...
Sam the T-man:
I've noticed that most in downloading lots. I don't know what's what in build mode anymore... I so wish everything got named properly - I know it's possible, as somewhere in there are clearly labelled files >_
Storygirl_24:
So in order to keep that file out when packaging sims etc. for the community, what should /could be done?
Most people package using Body Shop with whatever XP you have. And then you can't go back because the older BS versions don't work once you install a new XP.
So is there another way to package? Or is there a work around to delete the file before packaging?
BeosBoxBoy:
storygirl, perhaps you posted before reading the thread?
Navigation
[0] Message Index
[#] Next page
[*] Previous page