Joseph_sw

thanks, i also hate xp for deliberately ignoring version info for that format.

well, since MS-DOS interrupt itself usualy only offer 32bit logical sectors addressing ... is it sufficient to have partitions that have less than 2^32 -1 sectors, where total sectors for that hard-drive actually exceeded that value?

well, thats true. i choose to clear way from paragon partition program, as i experienced this disaster when i tried to resize the cluster size. my knowledge using diskedit and delphi allow me to learn how the errors occured/formed and able to salvages about 7/8 of the content. the paragon partion manager wrote the wrong first cluster mark on every file/folder entry in every directory clusters, what would happend if i allow scandisk to repairs that error?? its offer rom-dos defragd, but it also states it doesn't support fat32. there also offfer defragw.exe which support fat32 when i download it, it turn out to be defragw.exe from winME. however i already using winme defrag, and its refuse to work with my partition. that one partition was about 80 GB with 4KBytes/cluster, and also contain a few .nrg files that larger than 3GB in size. i'm curious about this statemnet: is this one won't be plaqued by "too-many-clusters-to-defrag" problem?but, i will try the free-dos one, since my cd burner and floppy drive is currently not functioning well, and its provide source code to examine. Thanks for the information.

quick defrag using defraggler, a NT based defragmenter software don't even touch fragmented directory clusters, nor you expect it to do optimization on removed entries (aka deleted files/folder entries) in directories entries. using old norton DiskEdit will reveals this fact. is there any FAT32 defragmenter apps that runs under true win98se dos? i wont mind the good ol' method if it would work under true dos.

i definetely hates js .write() function especialy if the parameter contains "<script " be it encoded/(un)escaped or not. i usualy use proxomitron to filter out most offensive script out there.

I'm aslo using 98SE2ME + RP9.6 + Kex 4.5 RC4 and using NetBEUI Protocol instead of NetBios over TCP/IP for file sharing purposes, i have no problem with that. however in the past i do encountering problem with ADSL modem which also provided a hub capacity (for shared connections). the hub part of that device rejects anything that is not TCP/UDP, so no IPS/IPX or NetBEUI for you, *rant* most likely the manufacture swallowed the whole 'tcp/ip is enough for all purpose' slogan campaign. */rant* i hope this was not you case though. NetBEUI usualy almost doesn't require any configuration, except probabaly you need to have same WORKGROUP in Network' Identification tab. and set access control to Share-level one. in some weird case, also check the NetBEUI properties just to make sure that 'File and Printer sharing' were already binded.

thats right, i just copied any "flash*10K*" files from networked winxp into my win98se. i never liked how adobe installer doing strange checks just to extract & registering an activeX control ..., but i find it amusing how adobe flash installer trying to beat KEX each time win9x user (with KEX help of course) able to install previous version of flash10.

for the ActiveX version, try registering the Flash10K.OCX using RegSvr32.exe that method works for me since Kex 4.5 RC1, and it remain so on RC4. Version Information on http://www.adobe.com/software/flash/about/ now said: You have version 10,1,85,3 installed

Great. I tried your suggestion, using Dependency Walker profiling, it works for me too! (both MameUI32 and MamePP) Now i can play that arcade emulator again with KernelEx RC4 installed. How did Dependency Walker able to bypass that error?

Thats faulty of XP' Local Security Settings. Control Panel -> Administrative Tools -> Local Security Policy -> Local Policies -> Security Options Look something like "Network access: " that has disable/enable settings fiddling with them could resolve it. (Usualy this: Network access: Do not allow annoymous enumeration of SAM accounts and shares. in my settings i change it to: Disabled, counter intuitive with double negative.) However, i also recomend to DISABLE "Remote Registry", in Control Panel -> Administrative Tools -> Services Before i disable that services, i've discover that other connected XP machine interfering with registry that revert my custom XP local security setings to their unconfortable 'default' settings. Some malicious malware also exploit that services too. Remote Registy .., i glad win9x doesn't have this stupidity.

i use the Mame Official Windows Binary Packages release from: http://mamedev.org/release.html It also have link for source code, and link for a few roms test (just copy/move the downloaded rom in .zip form to roms directory). To clarify per MSFN rule, respective Owner of that roms, gives their explicit permision for MameDev to host their roms images there. i already try the "Disable Custom Heap" option as well any others in KernelEx compatibility settings tabs, none of it solve the Mame problem on RC1 / RC3 release, i got the same result. To replicate the error simply try to run the MAMEPP.EXE Should nothing goes wrong, Mame should give the list of random selection of available roms from roms directory. However with RC1/RC3 i got ta Message saying "Out of Memory!", then exit the Mame.

i lucky enough to grab the Kex 4.5 RC3 before it got withdrawed. i installed on my system {English 98SE, with 98SE2ME + NUSB 3.3 + RP 9.6.6} so far i haven't encountered any problem with it. The RC3 still have the same behaviour as RC1 thats makes MAME spiting "Out of Memory!" exception error, regarless compatibly settings. Downgrade to beta2 make MAME works, but obviously flash10 is not working with beta2, so i keep the RC3 instead.

KEX-4.5-RC1 is cool, regsvr32 now works properly for many .ocx/.dll, for example: 'regsvr32 flash10h.ocx' now just simply works. however, this release also raises (std::bad_alloc &) exception error, that makes M.A.M.E decided to terminate its process. Mame source-code: http://mamedev.org/release.html i'm using MemeUI32 which is a Mame front-end that integrated with the main mame core: http://www.mameui.info/ the exception error doesn't happen if i fall back to KEX-4.5-Beta2. codes from mame's machine.c ... catch (std::bad_alloc &) { mame_printf_error("Out of memory!\n"); error = MAMERR_FATALERROR; } ...Mame gives me "Out of memory!" messages box error when i tried to run the roms, with Kex 4.5 RC1.

in one win98SE machine, i can't use any usb flash disk, it just gives usual blue-screen Exception Error 0E xxxx:xxxxxx IOS (4) vxd stuff. however, after checking bootlog.txt content i found suspicious entry: [0015EE7A] Dynamic load failed C:\WINDOWS\system\IOSUBSYS\intelvsd.vxd : [0015EE7A] Not a valid device - possibly corrupt after removing that file from IOSUBSYS directory (renaming it into antyhing_else.vxd, wont work), NUSB is now fully functional in that machine. minimum API requirement checking can be done using wdmcheck under win9x system.

i having trouble when i tried to select some texts by click-drag on this forum, this forum get un-responsive for couples seconds to a few minutes, happen only on new forum though, never happen before the upgrade. so, my temporary workaround is to add www.msfn.org into restricted sites zone. sure i lost many functionality what the new forum offer, but it makes this forum more browseable.