Well I find it much more practical actually.
I don't have a sound card in the pc yet nor a cdrom compatible IDE controller anyways, so network is the way to go.
I use it on my 3 vintage computers with no pb (now :p)
I can't really spend my time copying stuff on 15 floppies or burning CDs when everything is one command away 😉

And tkanks for interrupting my monologue, I was starting to feel lonely 😉

Yeah it sound easier (drag and drop files is faster), it has been months since I buyed an ISA NIC for my DX4 as well but never took the time to give it a try...
I think that 4 cards on the motherboard is already enough for now 😁 Don't really want to play with jumpers again for avoiding IRQ/IO/DMA conflicts (don't have any informations about my VLB controler card jumper settings, I searched for days with no results, trying some look a like models with no success 😵 ), it work like it should and I really want to leave it like that 🤣

sunaiac wrote:

Hint for others : type "image" in mtcp ftp client to avoid the ascii mode screwing everything ...
I tested sio many hardware setups just because of a configuration proclem ... 🙁

Well at least it's done 😀

Sorry, but that is a classic FTP user error - transferring things in ASCII mode instead of BINARY mode ...

You won't make that mistake again. But another good technique is to Zip things before transferring them. You may not need the compression, but Zip will tell you when the file has been corrupted in the transfer process. The type of corruption you caused with ASCII mode would have shown up immediately. MD5 sums are another technique to ensure good file transfers.

mbbrutman wrote:

sunaiac wrote:

Hint for others : type "image" in mtcp ftp client to avoid the ascii mode screwing everything ...
I tested sio many hardware setups just because of a configuration proclem ... 🙁

Well at least it's done 😀

Sorry, but that is a classic FTP user error - transferring things in ASCII mode instead of BINARY mode ...

You won't make that mistake again. But another good technique is to Zip things before transferring them. You may not need the compression, but Zip will tell you when the file has been corrupted in the transfer process. The type of corruption you caused with ASCII mode would have shown up immediately. MD5 sums are another technique to ensure good file transfers.

Hello,

I actually transfered a zip (phil's VGA benchmark), and that's what put me on the right track 😀
I really don't understand why mTCP defaults to ASCII thus.
windows does not, nor any other ftp client I used previously to my knowledge.
Is it supposed to be the default in the ftp norm ?
I'd rather have destroyed text than faulty exes with no clearer message than a reboot 😖
Would have lost 2 less days 😀

sunaiac wrote:

Hello, […]
Show full quote

Hello,

I actually transfered a zip (phil's VGA benchmark), and that's what put me on the right track 😀
I really don't understand why mTCP defaults to ASCII thus.
windows does not, nor any other ftp client I used previously to my knowledge.
Is it supposed to be the default in the ftp norm ?
I'd rather have destroyed text than faulty exes with no clearer message than a reboot 😖
Would have lost 2 less days 😀

That's part of the problem. This is *not* an mTCP problem. The FTP server sets the default transfer mode, not the FTP client.

A lot of clients will "stuff" an IMAGE command automatically into the command stream automatically before starting a file transfer. I'm not a big fan of automatic behaviors like that. The mTCP FTP client behaves like a bog-standard FTP client, and this is the correct behavior.

Better/more recent FTP servers just assuming BINARY is the default, which is rational.

Ok, I understand.

previously I used a simple filezilla on windows.
I recently switched to some ftp server on my linux NAS directly, it must be behaving differently 😀

Thanks for the input.

sunaiac wrote:

which configuration would you use, this my mother board doesn't clearly support write back DX4 : http://www.elhvb.com/supportbios.info/Archive … 19htm/419dz.htm

The Intel DX4 &E... column with just the writeback jumper set as in the P24D column ?

Ok, I've tried all combinations I could think of for my intel DX4, and even used a SV8B from AMD which is supposedly supported "officially" by the MB, but I couldn't get Write Back to work. Chkcpu always report write through, and bench results stay the same.

Any ideas ?

sunaiac wrote:

Ok, I understand. […]
Show full quote

Ok, I understand.

previously I used a simple filezilla on windows.
I recently switched to some ftp server on my linux NAS directly, it must be behaving differently 😀

Thanks for the input.

After thinking about this for a bit I'm going to add a warning to the client; if the client is in ASCII mode and tries to transfer anything that is not *TXT that is a signal that there might be a problem. This might save somebody else from this pain down the road.

sunaiac wrote:

sunaiac wrote:

which configuration would you use, this my mother board doesn't clearly support write back DX4 : http://www.elhvb.com/supportbios.info/Archive … 19htm/419dz.htm

The Intel DX4 &E... column with just the writeback jumper set as in the P24D column ?

Ok, I've tried all combinations I could think of for my intel DX4, and even used a SV8B from AMD which is supposedly supported "officially" by the MB, but I couldn't get Write Back to work. Chkcpu always report write through, and bench results stay the same.

Any ideas ?

That should do it, checking jumpers settings on stason for a similar board show that's the way to go... Is there some cpu caching settings under the BIOS ? Maybe upgrading to an updated bios could solve the problem (maybe it has been removed from the BIOS at the last minute by the manufacturer for stability concerns...)

Yes, there is a bios option, which doesn't seem to change anything 🙁

I asked FGB for some help, he's the previous owner of that board, hope he remembers if he had WB working.

BIOS can't be upgraded easily, it's not rewritable.

sunaiac wrote:

BIOS can't be upgraded easily, it's not rewritable.

Ask keropi, he might help you out if you have the BIOS file.

Time to bring an update about that target list 😁

- Intel 486DX4-100 SK096 Write Back --> still the same, only I now have 3 CPUs sintead of one, just "in case"
- Shuttle HOT 419 R2 --> begins to slowly but surely annoy me, but not on the hook yet
- 256KB cache --> no plan to upgrade to 512k anymore, if I don't change the mother board for one with interleaved 512kb
- 32MB FPM RAM --> down from 64. I just don't see the point of 64 actually, except slower startup.
- Tseng Labs ET4000/W32p VLB --> no change. Tested a bunch of cards, that's the queen.
- Sound blaster AWE32 CT3900, 32MB RAM, XR385 Wavetable --> no change. no ram found yet. XR385 rox in doom 😁
- Sound Blaster AWE 64 Gold for the MT-32/SC-88 --> I'm short on AWE64G right now (see signature), maybe a SB16 meanwhile
- Tekram DC680-T --> Liked the appearance of the card better than the Adaptec AHA2842A VLB SCSI ^^
- 4GB IDE HDD
- CDROM 52x IDE --> must find a pre-CAV CDROM drive, I only have a noisy 52x...
- DOS 6.22 ---> no need for windows 3.11, and win95 is on the P133
- linksys ether ISA LAN card for FTP transfer

Still need a descent box with 3 digit LCD MHz display 😀

vetz wrote:

sunaiac wrote:

BIOS can't be upgraded easily, it's not rewritable.

Ask keropi, he might help you out if you have the BIOS file.

Oh OK, I will, I did find a bios supposed to be compatible (but it's unclear if it's for R2 or R3 revision)

Tnaks 😀

I just sold a DC680-T on ebay. Never got to use it, is it a decent controller?

senrew wrote:

I just sold a DC680-T on ebay. Never got to use it, is it a decent controller?

Well it's not liked I benched it much, so I can't really compare.
I just find it very good looking 😁
All I did was install DOS, do a few ftp transfers and loop through phil's VGA benchmark to test all my video cards.
It's like smartdrv, but without smartdrv loaded 😀

Hi,
I cannot remember the jumper settings for WB cache off my head but it should be documented in the manual. I think I remember that I had a IntelDX4 running @ WB mode on this board. Of course you will need the right DX4, the "&E" part is write through, only the "&EW" is write back.
Anyways, I think the WB L1 cache scheme is much overrated. WB enhances the L1 speed but decreases the memory throughput. Write through gives you more memory bandwidth. For example Doom and games like this run a bit faster @ write through mode.

Hope that helps,
Fabian

Hello,

I'm currently using a &EW, I tested two others (in case I had a fake one 😁) as well as a SV8B 🙁
No luck yet 😖 Ordered a real P24D DX2-66 also, to try 😀
Well if you recall managing to get it working, I must just be doing something wrong.

I'm not really doing it for performances, gaining 5% performance is not really useful on a DX4 😁
It's for science :p

In terms of shooters it is more likely losing 5% rather than gaining them. Well I cannot reconstruct the settings. I once had another board but sold it. Maybe I'm able to contact the buyer and ask for the ysettings he uses.

Ok thanks 😀
And send me a PM when you get rid of the R3 ;p