Topic: X2 BIOS Build 4978 - Built in FTP (Read 3511 times)

BenJeremy · « **Reply #30 on:** August 22, 2003, 07:10:00 AM »

QUOTE (heinrich @ Aug 22 2003, 11:06 AM)

I decided to see what this thing can do, and tried to FTP u64x, and roms to f:

After a few hundred megs I got this:

CODE

421 Out of memory

I tried reconnecting, and resuming the transfer:

CODE

150 File status okay; about to open data connection.
421 Out of memory.

So, while this is great for loading a dash on the xbox, or when something goes wrong, to fix filenames or something (I wonder how this bios handles error 16 (time), if it boots the FTP server before that kicks in), Large files might not be an option right now.

Sounds like a resource leak.

I better wrap up my new FTP Server code

The new stuff for MXM should be very clean and will, of course, be as fast and compatible as the current MXM FTP Server, just better at handling aborts and a hair more 'powerful' (as well as more portable)

Xeero · « **Reply #31 on:** August 22, 2003, 07:17:00 AM »

QUOTE (heinrich @ Aug 22 2003, 11:06 AM)

I decided to see what this thing can do, and tried to FTP u64x, and roms to f:

After a few hundred megs I got this:

CODE

421 Out of memory

I tried reconnecting, and resuming the transfer:

CODE

150 File status okay; about to open data connection.
421 Out of memory.

So, while this is great for loading a dash on the xbox, or when something goes wrong, to fix filenames or something (I wonder how this bios handles error 16 (time), if it boots the FTP server before that kicks in), Large files might not be an option right now.

I'm assuming this is something that Team Xecuter can remedy with a tweak. We know that EvoX and other FTP-enabled dashboards don't use a swap file for their FTP functions, so they're all using the system memory just like the BIOS must be. I doubt that the larger BIOS size (and more consumed shadow RAM) has a direct impact on the memory required by the FTP functions.

heinrich · « **Reply #32 on:** August 22, 2003, 07:12:00 AM »

QUOTE (Xeero @ Aug 22 2003, 11:06 AM)

QUOTE (heinrich @ Aug 22 2003, 10:41 AM)

OK

I have the bios running right now.

The ftpd DOES NOT RUN ALL THE TIME.

XEERO was right in this.

You Press A, a nice X^3 FTP SERVER screen pops up, and there you are. So, no, you cant ftp to xbox while playing halo

Can you do me a favor and open the BIOS image up in X2BM, if you have it available? I'd be interested to see if it sees it as 1024K image or 2 x 512K images. 768K seems kind of bloated for a basic FTPd.

BenJeremy · « **Reply #33 on:** August 22, 2003, 07:21:00 AM »

QUOTE (Xeero @ Aug 22 2003, 11:10 AM)

QUOTE (heinrich @ Aug 22 2003, 11:06 AM)

I decided to see what this thing can do, and tried to FTP u64x, and roms to f:

After a few hundred megs I got this:

CODE

421 Out of memory

I tried reconnecting, and resuming the transfer:

CODE

150 File status okay; about to open data connection.
421 Out of memory.

So, while this is great for loading a dash on the xbox, or when something goes wrong, to fix filenames or something (I wonder how this bios handles error 16 (time), if it boots the FTP server before that kicks in), Large files might not be an option right now.

I'm assuming this is something that Team Xecuter can remedy with a tweak. We know that EvoX and other FTP-enabled dashboards don't use a swap file for their FTP functions, so they're all using the system memory just like the BIOS must be. I doubt that the larger BIOS size (and more consumed shadow RAM) has a direct impact on the memory required by the FTP functions.

Typically, I allocate a data buffer for each session, which is used to shuttle data for both incoming and outgoig transfers. There is no need to re-allocate new buffers (In fact, I was going to make this buffer user-adjustable in a future release).

They may be allocating a buffer for every transfer and not releasing it properly when done.

My "new" FTP Server is being developed in a Win32 app first... gives me a good opportunity to spot memory and resource leaks. The code will be portable to other Xbox apps, and I am considering a special "FTP Server" source code release separate from MXM so that others can use the code in their own projects without having to decipher MXM's code and untangling it.

BenJeremy · « **Reply #34 on:** August 22, 2003, 07:16:00 AM »

QUOTE (heinrich @ Aug 22 2003, 11:12 AM)

QUOTE (Xeero @ Aug 22 2003, 11:06 AM)

QUOTE (heinrich @ Aug 22 2003, 10:41 AM)

OK

I have the bios running right now.

The ftpd DOES NOT RUN ALL THE TIME.

XEERO was right in this.

You Press A, a nice X^3 FTP SERVER screen pops up, and there you are. So, no, you cant ftp to xbox while playing halo

Can you do me a favor and open the BIOS image up in X2BM, if you have it available? I'd be interested to see if it sees it as 1024K image or 2 x 512K images. 768K seems kind of bloated for a basic FTPd.

Well, I might load it up on the "family" machine, but the Dev box is an X2 Pro... and I need the Debug BIOS for development.

Xeero · « **Reply #35 on:** August 22, 2003, 07:26:00 AM »

So there's no cutting that 1MB down, eh? Wow. They should deem this the first X3 BIOS.

I may have spoken too soon when I said 2MB was overkill. At the time I figured the FTPd could fit into another 256K. Guess not.

Ubergeek had joked one time about using a 4MB flash ROM with the X3s. Maybe it's no longer joke-worthy.

warbeast · « **Reply #36 on:** August 22, 2003, 07:27:00 AM »

anyone with live and tsops flashed wont like this! i have a x2pro2.2 and i use debug but ill flash the tsops to have 2mb or use phoenix as a app to load the bios before a pay out for a x-bit

ps it looks like the new x3 will have a 2mb chip to due to the new bios

heinrich · « **Reply #37 on:** August 22, 2003, 07:27:00 AM »

Always that Phoenix Bios loader.....
I think it will be getting a little more attention now that everyone's chips are filled up.

BenJeremy · « **Reply #38 on:** August 22, 2003, 07:31:00 AM »

My current Win32 FTP Server test app weighs in @ 397k, which probably includes a bit of overhead, but not much.

insertjokehere · « **Reply #39 on:** August 22, 2003, 07:31:00 AM »

Just a thought... As the original MS Bios is 1024k, If you had a bigger BIOS, surely Memory hungrey games and proggys will crash when using a bigger BIOS. BIOS devs will have to cut the size down in order to keep memory space. Correct me if I am wrong

QUOTE

I may have spoken too soon when I said 2MB was overkill

I thought that 1mb was enough a day ago!

warbeast · « **Reply #40 on:** August 22, 2003, 07:34:00 AM »

maybe it can be made 256k? making it 1mb only would be a good way to stop matrix and other 256k mod chips wouldnt it!?!?

Xeero · « **Reply #41 on:** August 22, 2003, 07:27:00 AM »

QUOTE (BenJeremy @ Aug 22 2003, 11:24 AM)

My current Win32 FTP Server test app weighs in @ 397k, which probably includes a bit of overhead, but not much.

I'm not a programmer, so 256K was my guess. In any case, 397K is different than 768K. However, if the FTP code went over 256K, they couldn't release a 513K BIOS, and 768K may also not be possible. 1024K may have been the next logical size.

mamajo · « **Reply #42 on:** August 22, 2003, 07:39:00 AM »

This is not fair!
How does a bios go from 256k to 1mb just by adding FTP?
Now if we want to enjoy all of the other features in the future we will have to upgrade to a X3 chip. *mamajo throws $100 on mod and instal in the garbage* oh wait I'm not that stupid.

feflicker · « **Reply #43 on:** August 22, 2003, 07:32:00 AM »

We need a hack

I am sure it will be out before I get home from work

Xeero · « **Reply #44 on:** August 22, 2003, 07:40:00 AM »

QUOTE (insertjokehere @ Aug 22 2003, 11:24 AM)

Just a thought... As the original MS Bios is 1024k, If you had a bigger BIOS, surely Memory hungrey games and proggys will crash when using a bigger BIOS. BIOS devs will have to cut the size down in order to keep memory space. Correct me if I am wrong

QUOTE

I may have spoken too soon when I said 2MB was overkill

I thought that 1mb was enough a day ago!

From what I know, the MCPX can only grab 1024K at a time, so we won't be seeing any BIOS releases over 1024K unless DMS decides to hack the MCPX.

Author Topic: X2 BIOS Build 4978 - Built in FTP (Read 3511 times)