Hack Build Fail

Well I'm trying to build a sonic 1 rom but I get 2 different messages. If the disassembly folder is placed in another foldere I get



SN 68k version 2.53

SO\SONIC1.ASM(1) : Error : Could not open file 'SO\SONIC1.ASM'


Lightning's ROM Padder


Reported Size: 0 Reported Checksum: 0


Size applied: 7F Checksum Applied: 0


Press any key to continue . . .



but if it's on the desktop I get



SN 68k version 2.53

The instruction at 00401dd2 referenced memory at 003b1000


The memory could not be written



I got this about a week or two ago and I didn't try to build again until now.


I don't what happened, I was able to build roms before. Please help me I really don't know what to do this time.

 

I think I once had that problem, the path was too long (it was something like f:\soned2\oldversions\sonic1 - 100210 - blablabla\). I made it shorter and it solved the problem.

 

Actually size doesn't matter. It seems you are using the ASM68k fix, were it doesn't matter how long the path is AFAIK.


However, the first problem should be pretty obvious: The compiler cannot open the sonic1.asm file (the main ASM file). You probably just renamed, moved or deleted it.

 

That's not the problem I have the ASM file in the Sonic 1 disassembly folder and it's called sonic1 and the only thing I I changed to the ASM file is I added the spindash. So I have no Idea what the problem is and I probably should have but posted this in the first post?

 

Rename your SONIC1.ASM(1) into SONIC1.ASM

 

Already called SONIC1.ASM

 

I suppose it's really in the so\ folder, right? I guess it is, but someone had to ask the question.


Do you have a backup of the file before you added the spindash? If so, does it compile correctly?


Are you sure there isn't a second extension? If your OS hides known extensions, there could be another (hidden) extension after the .asm.

 

it's not in an so/ folder I don't even have an so/ folder. I've tried to build with clean disassemblies with no luck.

 

If a clean disassembly doesn't work, i can suggest two things.


One, keep your assembly as close to the root of the drive as possible. I suggest C:/Hacking or something. If that does nothing--it may be something with cmd. A version of windows I had, some form of malware corrupted the registry I'm assuming, and rendered any cmd commands useless.

 

Maybe someone can confirm what's that "SO\" in the error message? It's written "SO\SONIC1.ASM", so I thought "so" was a folder :blink:


By the way, did you check the batch file? I won't post mine since we aren't using the same version, but the path to the file may be wrong.

 

Ya, there is something wrong with the cmd is there anyway to fix it without wiping the harddrive?

 

Are you sure your cmd itself is really the problem? That would be pretty odd (which does not mean that it's impossible, as Irixion already said). If I were you, I would test a bit with the cmd to look if that's really the reason. This video contains some cmd releated stuff, you might wanna check out first. Other than that, no idea what to do.

 

Do you mind posting a print screen of your folder?

 

what do you mean? I have the disassembly folder in another folder with all my hacking tools so which folder do you want? Also do you mean you just want a picture of what's in the folder?

 

He means like this: http://sitemaker.umich.edu/imdocs/files/folder.jpg *Runs*


Serious note: This seems very odd, could you maybe send us a copy of the batch file? (i.e. "Build.bat"), we can analyse what's wrong with it.

 

You mean this:build.rar

 

Hmm, this is dodgy, I'm not sure how or why it presented this...

...when it's clear to me that...



asm68k /o op+ /o os+ /o ow+ /o oz+ /o oaq+ /o osq+ /o omq+ /p /o ae- sonic1.asm, s1built.bin



...it's reading the source not from inside a "SO" folder, very strange, as "Dandaman955" said, could you maybe take a screen shot of all the contents where your "Build.bat" file is?

 

Have you tried moving the entire Disassembly (Nothing else) onto your desktop, and then trying to build the ROM from there?

 

Ho ho, real funny. ¬_¬


But yeah, a screenshot of your disassembly was what we want.

 

Damn, you beat me to it! I was going to put something like that! D:


Haha, anyway. I had a similar problem to... All I did was move my whole source to some other part of my computer and eventually it worked. =P