"Import Entire History"

[captkirk685]

Originally Posted by KCRoyalsFan

It is supposed to be more accurate as far as when players really entered the league.

I assume a google search will bring it up? It might be worth the wait one of these nights I can just set them after I go to bed...

[KCRoyalsFan]

they should be on padre's mod site

http://www.padresfanmods.net/

[captkirk685]

Originally Posted by KCRoyalsFan

they should be on padre's mod site

http://www.padresfanmods.net/

Thanks for that link, might be a dumb question but can you use both data bases in the game?

[CHCfan]

Originally Posted by battists

I think some of the historical databases behave differently.
Not confirmed, but I've seen at least one person (Bobbuttons) have it basically never finish using Gambo's, and finish quickly with Lahman 54.

If you're having this issue, I'd say try Lahman 54. If it's still not working, come look for the thread about this in Tech Support, and join the discussion.

The expectation is that you should be able to import up to modern days within I'd say an hour or so, with the obvious caveat that everyone has different hardware. I mean, basically, if you leave it for six hours, and it's at 2% done, that's not right.

I'll give that a try, Steve. Strange solution -- any idea on the reasoning behing it -- not that it matters, as long as it works.

[Kelric]

Originally Posted by captkirk685

Thanks for that link, might be a dumb question but can you use both data bases in the game?

Yes, though obviously not in the same league (unless you alternate years, I suppose). Just put them in different folders and remember which one is where when you want to import.

[Mikekem]

Originally Posted by battists

I think some of the historical databases behave differently.
Not confirmed, but I've seen at least one person (Bobbuttons) have it basically never finish using Gambo's, and finish quickly with Lahman 54.

If you're having this issue, I'd say try Lahman 54. If it's still not working, come look for the thread about this in Tech Support, and join the discussion.

The expectation is that you should be able to import up to modern days within I'd say an hour or so, with the obvious caveat that everyone has different hardware. I mean, basically, if you leave it for six hours, and it's at 2% done, that's not right.

I was able to import up to 1983 with Lahman 5.4 with full history in under 8 minutes. Gotta love the dual core with 2 gigs of memory.

[Bobbuttons]

Originally Posted by battists

I think some of the historical databases behave differently.
Not confirmed, but I've seen at least one person (Bobbuttons) have it basically never finish using Gambo's, and finish quickly with Lahman 54.

If you're having this issue, I'd say try Lahman 54. If it's still not working, come look for the thread about this in Tech Support, and join the discussion.

The expectation is that you should be able to import up to modern days within I'd say an hour or so, with the obvious caveat that everyone has different hardware. I mean, basically, if you leave it for six hours, and it's at 2% done, that's not right.

Okay, now that I played with it all yesterday and then just got off work, I'll fill you in. I haven't really gotten it to work with Lahman 5.4, per se, as it still seems to take forever, and I haven't gotten a late MLB season imported yet. I'll try to upload a season between 1970 and 1980 tonight sometime with the Lahman DB and let you know if it's any better. Wish I could get it to work, though. I would love to take over my Indians in 1994 with the full history imported.

[Gambo]

I really don't understand the 8 hour difference. The database is only 3x larger than lahman (understatement). It uses the exact same format as any other database.

I think the issue is possibly that you are doing the import for 1985 etc without doing the cutting and pasting I recommend in the readme. (I really should make it a requirement and not a suggestion) this way the database will be trimmed to a more manageable size. Also, if you want to import the entire league history, and you dont do the cutting and pasting from Lahman the numbers and info will be wrong.

[tward13]

Originally Posted by Gambo

I really don't understand the 8 hour difference. The database is only 3x larger than lahman (understatement). It uses the exact same format as any other database.

I think the issue is possibly that you are doing the import for 1985 etc without doing the cutting and pasting I recommend in the readme. (I really should make it a requirement and not a suggestion) this way the database will be trimmed to a more manageable size. Also, if you want to import the entire league history, and you dont do the cutting and pasting from Lahman the numbers and info will be wrong.

I did the cutting and pasting. Never got past 75% before the computer locked up.

[SWardle]

It took my computer 3 minutes and 13 seconds to import to 1981. I have this setup.

AMD Athlon 64 3200+ Venice (Overclocked)
2 gigs of ram (also overclocked)
10,000 RPM SATA Harddrive

I built my computer from scratch for surprisingly cheap. Almost every part aside from the case and power supply was bought off Newegg.com.

[Bobbuttons]

Okay, so my three year old computer with 512 MB of ram an 2.4 GHz processor tried for 16 hours to load 1994. It got all of 13% done. There are NASA programs that would run on my computer faster.

[battists]

I'm going to move this thread over to Tech Support. We need to figure out what it is that is causing this issue. That's unacceptable time, of course.

[chippered]

Thought I'd chime in with my own problems. Using Lahman 5.4, Its freezing on me anytime I try to import past 1990 or so. Using 1950 as my import date, with full history, only took a few minutes. I'm a fictional player, but I'd really like to take over in 2006 and use the cubs from there and the league would, eventually, be a fictional league, but it would have all the history of the real majors. But thus far, its not possible. Oh, and I have a dell, only a couple years old. Dont really know all of the specifics off the top of my head, but can get them if needed.

[Aceshigh24]

So has anyone been able to fix the solution to this problem or does it lie with the memory of the computer.....Do i need to go out and purchase a gig of memory to get this sucker to work?

[rasnell]

This one may be hard to figure out since it has always worked fine for some folks and not at all for others.

The other odd trend we're seeing is no problem with Lahman for some and all kinds of problems with the Gambo database. That doesn't make sense since the fields would be the same but only the data might vary.

I wished this would work for everyone because it's a fantastic feature. Even when it's working well on my PC, it does take quite sometime to import the complete history up to the 1990s. That's an awful lot of data and info to import. I usually run it and go do other chores before coming back. About the only time I actually get up from the game and get a break.

[Gambo]

The only other times i've seen issues like this have to do with the amount of expanded memory Windows allows for the system (of course that was pre-XP)

I'd check the size of your paging file in XP... mine is 2046 MB

[Comedian2004]

As mentioned earlier, get rid of anything running in the background, defrag, do whatever you can do get it running it's best.

Restart the computer, disable anything that is not essential in memory (real radio, AOL CRAP, IM, etc.)

Then launch it, let it do it's thing, go visit the neighbors and offer freshly baked chochate cookies and milk. Come back, and see how it is doing.

It will pretty much max out your ram, and it could possibly go into virtual mode when doing it's thing. If that happens, after it is complete, exit the game and reboot and then go play the game. Windows runs slower after VM kicks in, even if the memory got cleared back up.

I use a free program called RAM BOOSTER (google it). It does a good job of cleaning up the memory to give you a little more.

[solarkev]

As I posted earlier, I am one of those that has a very slow history import issue. I have 512MB and about a ~2 Gig processor. I reach about 13% player import after 15 hours. Not much difference between Lahman or Gambo databases. I tried doubling my page file (using XP), no difference. I tried Ram Booster, no detectable difference either. My machine is quite clean of running programs.

Are we learning that more than 512MB is needed?

[Cardinal Rule]

I'm using the demo, but I'm also running into this problem. I've had OOTP3, 4, 6, and 6.5 but didn't opt for 2006. 2007 has a LOT of the features I've been wanting, so I dl'ed the demo and plan to buy the game when the demo expires.

I had some spare time last night, so I ran a few tests to see if I could learn anything more about it. First of all, here are my system specs:

P4 2.0G with 512MB RAM, Windows XP
Ran a Perfect Disk defrag, closed all background apps possible other than my firewall (Comodo). Increased my virtual memory size to 3x my RAM, disabled System Restore and did a few other tweaks to improve available system resources. My commit charge before loading the game was 230M/2018M. I have found no other problems with the game in my tests.

Here are the tests I ran, all using Lahman 5.4 from the historical league wizard:

1920 season import, with complete history, based on remaining career, all other options default. Completed database load and player import in less than 30 minutes.

1940 season import, with complete history, based on remaining career, all other options default. Completed database load and player import in about 30 minutes.

1970 season import, with complete history, based on remaining career, all other options default. Completed database load and player import in about 1 hour.

1979 season import, with complete history, based on remaining career, all other options default. Completed database load, but stuck on 0% player import after 1 hour.

1980 season import, with complete history, based on remaining career, all other options default. Completed database load, but stuck on 0% player import after 1 hour.

2004 season import, with complete history, based on entire career, all other options default. Completed the database load, but stuck at 0% player import after 2 hours.

I actually tried the 2004 import before doing the steps to free up system resources, and would get the low virtual memory popup after about 30 minutes. After freeing up the system resources, I did not get the low virtual memory popup on the same import, but it still did not advance beyond 0% player import.

So from this it seems that there is some problem either with my available system resources, the database itself, or the game, when trying to import at least anything from 1979 on. I would expect the 1979 import to take longer than the 1970 import, but I would also expect it to advance beyond 0% in the time I gave it before killing the process and re-booting unless it's completely overwhelmed my system.

I would hope somehow this can be figured out as I would love to be able to use this feature.

Let me know if I can provide any more info to help out.

[battists]

Originally Posted by Cardinal Rule

So from this it seems that there is some problem either with my available system resources, the database itself, or the game, when trying to import at least anything from 1979 on. I would expect the 1979 import to take longer than the 1970 import, but I would also expect it to advance beyond 0% in the time I gave it before killing the process and re-booting unless it's completely overwhelmed my system..

Thanks Cardinal Rule, this is great data.

Although, regarding the bolded section above, your data looks to me like it points to a problem with something between 1970 and 1979 causing the problem. That is, 1970 worked fine, 1979 doesn't.

So, there could be some problem with the data (or the program) in the years between 1971 and 1979 that is causing the issue.

Since you've volunteered, any chance you'd care to repeat your test one year at a time, starting at 1971 and going up to 1978, to see at which specific year it dies?

Steve