Robin Hoods Playground

So I am still a beginner at this but not completely without knowledge, but I gotta say this has completely stumped me.

Every time I boot up iPrep on my flash drive and either turn on my 360 drive or when it goes to read the drive, it will give me the internal stack overflow error and completely halt the process. For example, if I leave my drive on the whole time while running iPrep, once I get to where it lists all the drives and asks if I would like to resend the command, it will freeze right before it gains access to the drive it is suppose to. If I turn off the drive before hand, and I hit y to resend, turn the power on... yep you guessed it, Internal stack overflow.

I am using a connectivity kit with iPrep v8.8 done in Windows XP 32-bit to an HP 2 GB flash drive.
No floppy in my computer so it is disabled in bios. I have also restored my default BIOS settings several times with same results.
I do have a VIA sata card and have tried different USB flash drives.
I have looked at the video tutorials to find out how to do it and although the videos are great, I still have no success.
I have tried iXtreme 1.51 and 1.5 neither worked

If any other info is needed please let me know

I have looked everywhere for a solution to this problem but I hope someone here can shed some light to me and show me the way. If you have any suggestions, please let me know as it will be greatly appreciated.

hi i think its something to do with your config.sys i had the same problem so
i uesed 360 mod disc downloaded from xbins in firmware tools hope this helps

Where does the error show up on? Is it an iPrep error or Windows error?

Stacks are reserved memory that programs use to process hardware events. A stack overflow occurs when there is not enough space in memory to run the hardware interrupt routines. To resolve these behaviors, you can modify the "STACKS=" line in the Config.sys file, eliminate terminate-and-stay-resident program (TSRs), and eliminate hardware conflicts.

But this is in Windows.... So i'm not sure why you are getting this because DOS and iPrep take minimal resources..

technoe wrote:Where does the error show up on? Is it an iPrep error or Windows error?

Occurs when listing the drives... as soon as it turns on i get the error.

Backslash wrote:

Stacks are reserved memory that programs use to process hardware events. A stack overflow occurs when there is not enough space in memory to run the hardware interrupt routines. To resolve these behaviors, you can modify the "STACKS=" line in the Config.sys file, eliminate terminate-and-stay-resident program (TSRs), and eliminate hardware conflicts.

But this is in Windows.... So i'm not sure why you are getting this because DOS and iPrep take minimal resources..

very true, but apparently having the drive turn on while on DOS is too much to handle... is there any way to make the stack go higher?

I will try the mod disc now and see if there is any different results

So just as an update:

Mod Disc Failed... kept getting stuck on reading the drive again, so my question is: Do I need to unlock the drive before I run iPrep? if I do then that was my problem.

I did manage to flash my drive with jungleflasher so I did manage to do it. Thank you everyone for trying to help.

nice man, that stack overflow thing is something else...

If you don't have a floppy drive installed on this computer, check the BIOS and make sure that the floppy is disabled.

sadalius wrote:If you don't have a floppy drive installed on this computer, check the BIOS and make sure that the floppy is disabled.

It was... I also had tried reseting the BIOS back to default and it did the same thing...

I think your BIOS just needs to be updated. If you've never flashed a BIOS before there are some key points to remember:
1. If you're going to update from Windows make sure nothing else is running that could interfere with the process.
2. Do you damndest to make sure you DO NOT LOSE POWER!!! If you lose power in the middle of an update you will have a giant paper weight under your desk.
3. Make double sure you have the right version.
4. If available download the original bios version from the manufacturer that in case you have issues with the new one you'll be able to revert back.

technoe wrote:I think your BIOS just needs to be updated. If you've never flashed a BIOS before there are some key points to remember:
1. If you're going to update from Windows make sure nothing else is running that could interfere with the process.
2. Do you damndest to make sure you DO NOT LOSE POWER!!! If you lose power in the middle of an update you will have a giant paper weight under your desk.
3. Make double sure you have the right version.
4. If available download the original bios version from the manufacturer that in case you have issues with the new one you'll be able to revert back.

Thanks a lot for the tip I will definitely be doing that to make this more easier in the future... I will look up the process on how to do it and keep those points in mind.

Ive seen this problem before and if i remember right its to do with your Raid setting in bios, try turning Raid off.

Hope that helps you out

looks like you have tried this but

Stack overflow
Most of the time this is fixed by resetting your bios to default.
One person did this.
"I went to the bios and i changed the IDE to RAID"
This also can be from a computer that does not have a floppy drive installed but, the floppy is enabled in the bios
Go in the bios and dic able the floppy.

complete list of Q&A read here
viewtopic.php?f=63&t=324&p=1379#p1379" onclick="window.open(this.href);return false;