The other day I got around to setting up a map for a friend currently on gooberdata with crome 1.0 which I understand is the prelude to CromePro.. anyways, after setting everything up on the map (3-bar GSR), I tried opening it with my burner program to burn it, but it keeps telling me the file size is too larger for that chip.. what give? Some kind of secret crome society trick? It only happend with that ver. crome maps, UD and older crome maps will burn fine.. anybody?

 

Its a problem with your burner setup, not crome. Make sure you have the correct type of chip selected in your burner setup. Goto PGMFI.org and get a newer version of crome. There are new features that help with some known issues in crome 1.0 and the 3 bar. Run 1.1.5 at a minimum, convert to P72 style map scalers, set the map cutoff (new in boosttools+) to 5 and you'll be golden.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by ITR981002 &raquo;</TD></TR><TR><TD CLASS="quote">Its a problem with your burner setup, not crome. Make sure you have the correct type of chip selected in your burner setup. Goto PGMFI.org and get a newer version of crome. There are new features that help with some known issues in crome 1.0 and the 3 bar. Run 1.1.5 at a minimum, convert to P72 style map scalers, set the map cutoff (new in boosttools+) to 5 and you'll be golden. </TD></TR></TABLE>

It's the same burner setup I've been using for a year or so now, I doubt that's the problem when every verson of UD and every other version of Crome works just fine..

I'll look for 1.1.5 now

 

I've never had a problem with Crome version 1.1.5 or 1.0. I'm using a Moates.net Burn1, I can't say that i'm familiar with any other type of burner, but I know people have had much better luck with later versions of crome and the 3 bar.

 

I use a willems burner.
Never tried the 3bar though

 

for some reason, Crome will sometimes save 64k files instead of 32k files.

If you look at the file with a hex editor, you'll see that the top and bottom 32k are identical. Use the first 32k and you're fine.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by blundar &raquo;</TD></TR><TR><TD CLASS="quote">for some reason, Crome will sometimes save 64k files instead of 32k files.

If you look at the file with a hex editor, you'll see that the top and bottom 32k are identical. Use the first 32k and you're fine.</TD></TR></TABLE>

..ehhh, how about I Email you the bin Dave and you tell me if that's what's going on because I have zero knowledge on hex editors and the last thing I need to do it chop up an otherwise useful file

 

You're on your own. Never too soon to learn. Sorry... Heading to Detroit for DEMF and a weekend of sex, drugs and techno.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by VTC_CiViC &raquo;</TD></TR><TR><TD CLASS="quote">

..ehhh, how about I Email you the bin Dave and you tell me if that's what's going on because I have zero knowledge on hex editors and the last thing I need to do it chop up an otherwise useful file </TD></TR></TABLE>

Just burn the 64k file on a SST27SF512 chip and you will be golden as well...or are you only using Amtels?

 

Are you making notes in the maps that you are making??
That might be causing the problem, happened to me before when I tried to make notes in the .bin that I was making.