div pack error

12/08/2010 02:30 ryufireblade#1
I am getting the following error when I try to create an update for the data.pak file:

Out of memory while expanding memory stream.

Is there a file size limit that the div packer with create divs for?

Yes I did you the search before I posted this thread.

Thanks in advance.
12/08/2010 02:44 daddycool.#2
Yeah, split your folders.. i don't remember well but i think the max size are 200mb or 300mb per pack
12/08/2010 03:25 ryufireblade#3
Quote:
Originally Posted by daddycool. View Post
Yeah, split your folders.. i don't remember well but i think the max size are 200mb or 300mb per pack
So it can't be done then. My pak file is around 3gb. Besides using WinHex or creating an online patch, what would be another possible way to update the pak file with a new IP address?
12/08/2010 04:47 daddycool.#4
I have said the max size of the folders you have to put in divs to update your data.pak and not the max size of the data.pak
12/08/2010 11:06 janvier123#5
Quote:
Originally Posted by ryufireblade View Post
what would be another possible way to update the pak file with a new IP address?
1. tell your ip adress to all members and let them change it by them selfs
2. make a new client
3. make a patch
4. get a dedi that does not change ip


i would got for nr4
12/09/2010 00:16 -8gX#6
@janvier what are you talking about lol. He doesnt need to do any of that.

@topic-All you have to do is do your patches in parts. If your using the normal DIV updater make sure your patches are in /data/data/share,texture etc. Also, always remember to open up 0000.div after you made the patch to ensure file names are correct.

IE. If you put maplist.csv in data/data/share/maplist.csv and run the updater; make sure you click the top button on the DIV tool named "Load DIV's" I think and select the first newly created DIV in the /div/ folder. It should populate the left side of the screen with /data/share/maplist.csv. BUT sometimes it will take of the 'd' in 'data' so it outputs /ata/share/maplist.csv. The fix for this is just adding another d in the original data folder. So when you redo your patch place maplist.csv in /data/ddata/share/maplist.csv and make sure you double check again.

So; to make a patch that is 3gb do as follows.

1. Separate the large folders from the rest, this is your action/texture and any other folders over 100mb.

2. action and texture are still to big. Open the texture folder for instance and CUT the first 2 folders inside that directory to your patcher /data/data/texture/2foldershere and run the patcher. Make sure to double check paths!

3. After double checking, rename the DIV folder to 20.0.12 or whatever patch number your on and put it in your HTDOCS or Public_HTML folder so the patch goes live.

4. Dont forget your history file.

5. Rinse and repeat for the other directories and files inside /texture/ and /action/ until nothing remains in those folders. This could be up to 7-8 different patches. So 20.0.12 - 20.0.18 could just be for the texture folder.

6. Make sure all paths are correct! I cannot stress this enough. If you unpack your data.pak and more that just a /data/ folder is in there. You probably did it wrong...

So theres a little tutorial to patch 3gb. It will take patience and getting used to but its what I did and you should learn it too.
12/09/2010 02:59 ryufireblade#7
Ok, I got smart. I modified the ip address in my channellist.csv and loginlist.csv from my unpacked client and created an update for those. Then I had to create a small patch and uploaded to our website to change the ip address for the auto-updater. Thanks for all your help. This thread can be closed.
12/09/2010 07:20 janvier123#8
you can use [Only registered and activated users can see links. Click Here To Register...] this and make a report

@-8gX
he wanted to know how to change ips, so i gave him a few options :)
12/09/2010 09:50 ~Kakkarot~#9
Quote:
Originally Posted by ryufireblade View Post
Ok, I got smart. I modified the ip address in my channellist.csv and loginlist.csv from my unpacked client and created an update for those. Then I had to create a small patch and uploaded to our website to change the ip address for the auto-updater. Thanks for all your help. This thread can be closed.
#closed