- 精华
- 0
- 帖子
- 10
- 威望
- 0 点
- 积分
- 10 点
- 种子
- 0 点
- 注册时间
- 2009-8-6
- 最后登录
- 2023-9-25
|
楼主 |
发表于 2017-9-4 13:58 · 广西
|
显示全部楼层
adsl95 发表于 2017-9-3 19:55
http://www.ps2-home.com/forum/viewtopic.php?t=1895
这个地址有个八月二十七号的版本
但是psx-scene却只 ...
你这网站是最新的更新了~
近期更新日志(Tentative CHANGELOG)如下:
wLaunchELF v4.43a (Build-2017-08-27)
- The poweroff issue [MISC/PS2PowerOff] was fixed, along with a PS2SDK update.
关机(MISC/PS2PowerOff)的问题已修复,PS2SDK也随之更新了。
- There is still an issue running [MISC/OSDSYS] -- it freezes the console -- should be fixed soon.
[MISC/OSDSYS]的问题(导致PS2假死)仍然存在,将很快得到修复。
(以下更新内容实在看不懂,无法继续翻译了,关于FTP相关功能的改进)
wLaunchELF v4.43a (Build-2017-08-26)
- Here is a small test, for those who were having problems with FTP transfers seizing up randomly with the PS2 still responsive (to controller input):
- Changes to LWIP options:
- 25 -> 32 PBUFs
- 8 -> 24 input TCPIP API messages (not for TCP/IP, but is used for passing messages to the "TCPIP" thread that handles packet input)
- Semaphores are created with the THPRI option
- This should also solve the issue with pings failing when the IOP is under heavy load.
wLaunchELF v4.43a (Build-2017-06-21)
- Here is a small test, for those who had problems with FTP support
- There was a problem with my tcpip.h header, which did not share the same values as the other headers from the 2 LWIP ports.
- I reckon that this standardization of values should solve the problem.
- There was also the workaround by the old ps2ftpd developers, which worked around the getstat/chstat glitch in PFS. Since that glitch was taken care of, I have removed the workaround. This will mean that if anyone does a directory list operation on the HDD unit, file sizes should be displayed.
wLaunchELF v4.43a (Build-2017-06-18)
- Fixed USB support on disks with no partition table (thumb drives).
- Fixed formatting of PFS partitions.
USB disks will only be mounted if they either contain a supported partition (i.e. FAT12/FAT16/FAT32). Mounting the whole disk will no longer be done, unless the disk is deemed to not have a valid MBR.
Previously, it would attempt to mount the disk, even if it had a valid MBR. This also led to cases of USB disks being improperly accessed, if they were formatted with some unsupported filesystem like exFAT.
I didn't find any standard that specified how the operating system can determine whether the disk contains a MBR or a VBR, which both have the same magic value in the exact same position (why???). But I did some experiments with Windows 10, which led me to conclude that Windows will at least check that for every valid (ID is not zero) partition entry:
- The starting LBA must not be zero.
- The starting LBA must exist within the disk.
There might have been some check against the size of the partition, but I did not manage to identify a pattern.
wLaunchELF v4.43a (Build-2017-06-17)
- Updated PFS module (improved reliability).
- Fixed power-off processing. All files will be closed and the expansion-bay deactivated, prior to power-off.
|
|