Jump to content

Offler

Member
  • Posts

    426
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Slovakia

Everything posted by Offler

  1. This theme is intended to be maximally neutral and be so much "win98" as possible http://slayershrine.wz.cz/nahlad.jpg Theme is still in development, but here is first version. buttons are sharp to look more like in Windows 98 instead of vista like polished buttons. theme is so much neutral as possible, without too much glitter on it. Any suggestions welcome added version 1.1 (sky9811.zip) sky98theme.rar sky9811.zip
  2. try to add umbfill from umbpci package as last file to your autoexec.bat. it will fix memory grabbing from Win. also i never encountered system with so much ram - i have 1,5gb ram. try to set maxfilecache to 32kb or fewer.
  3. ok. right now i have passed almost all tests i have required with my own system. few apps which can be ommitted have been removed from project so i am able to push the project to second phase. i shall ask some my friends if they wish to install windows 98SE with patches (on first page) and see what the system does and how it looks. in this case i shall ask some friends which are not IT skilled. their references shall be used in further development i hope so... also some suggestions current "evolved" windows 98SE miss some things: - support for hyperthreading (p4 with HT) - support for multithreading (dual core and higher) - large ram (partially fixed by commercial product) - hi cpu speeds (what about test with low speed dualcore? has anybody tried this and measured core performance?) - driver support (limited by manufacturers, but quite good when searching for all wdm standard drivers) - files larger than 4gb (NTFS can be applied but window stil cannot write more than 4gb) this is just very mad question... but... can be these things solved for future?
  4. well... i am not looking for dual boot solutions or for pc restor tool. I have backups on my secondary harddisk. also i dont want my MP4 player as bootable drive - at least not for now the problem is really only with USB driver which is acting very strange... the "Unknown device" is hardly any kind of device with which can win98 communicate. maybe the communications protocol in USB is a bit different between win9x and WinXP when it comes to driverss. edit: the same problem repeated in XP... so i believe that it has no problem with win9x drivers.
  5. so i have identified the problem - for now i have way how to connect the device to my computer... Normal behaviour 1. I plug in the device 2. "Rock MP3" has been detected 3. Install it as Mass Storage device 4. other USB devices have been detected and installed (USB disks) 5. "USB Device" is identified as "Unknown Device" and being installed. The device is Turned off (red cross in device manager). It seems that the unknown device should not be active but it is and it disconnect USB Mass storage. There is a way how to connect the device: 1. Erase USB.INF from c:\windows\inf directory 2. Plug in device 3."Rock MP3" has been detected 4. Install it as Mass Storage device 5. other USB device have been installed 6. "USB device" has been detected, but not automatically installed. 7. Unplug the device. 8. Choose "Cancel" in device installation dialog. anytime when "USB Device" is detected repeat it... i have never seen worse behaviour any help? maybe patch to USB.INF or other patch. when "Unknown device" is detected and installed the "Mass Storage Device" is stopped and seems like disabled. Maybe there is a bug which disables Mass storage instead of unknown device...
  6. two days ago i bought this mp4 player. on box was written that it supports windows 98 so i wanted to know how much is it true. 1. Install I used mix of NUSB and original drivers. Device installed correctly and i was able to access internal flash drive in it. When i replugin the device there was detected another new usb device and it was automatically identified as "Unknown device". while the localization was here slovak this means that there was used standard win98se driver. after that i was unable to acess flash drive and the device switched to "charging mode" 2. Install i restored system from backup and tried installation only with original drivers. i failed. 3. Install system restored and i tried to use only NUSB drivers but failed again. the only way how to make the device work is to use both drivers. 4. Install I restored system from backup and installed both drivers again. The device driver (USB Mass Storage) must be installed without reboot or the device shall disconnect and some parts of driver will not be functional. For this reason a correct driver must be already ported in windows. In driver package from manufacturer is one USB Mass Storage driver which is dated 18.4.2007 and use usbntmap.sys this one is the correct driver and other (older) should not work. also because system sometimes (in most cases) detect new phantom device called "Unknown device" i removed usb.inf file from system. this allowed me to install driver of my choice. i tried it with mass storage device but it seems that it failed... it seems that this is also a Mass Storage device but it doesnt seems to work. if this unknown device is being detected it means that all connections already maded are lost. also USB mass storage device will become invisible from device manager. I suspect that that unknown device is mass storage, but it is not correctly identified. MP4 player maybe sends fake signals or windows cannot identify it properly. i try to use unknown device identifier but i think it will not help.
  7. check bios settings. for this situations try defaults, but if you dont have fdd drive dont forget to set it up. also take care about drivers. if you casn acess safe mode it means that problem is surely in one driver which may conflit with app.
  8. my logo is 2bytes larger. dont know why. (256 colors, 640x, version unknown) the message on background was no error message. it was info that updates are being installed (classical info while installing anything)
  9. is the dos scandisk during bootup really needed? i experienced more issues with it than with win version (more data lost, more trouble created as cured). WBL tested: positives: - can be executed from autoexec.bat (in this case doesnt need patched io and command) - works with buffers=99,8 negatives: - does not work with my logos (wrong size), and with svgacom logos - system reboots when text is displayed from behind - text from backround overlays the original screen
  10. My system is not pure Win98SE machine. i use it because i really like full dos support. no emulators. Dos provide me also browsing where i can visit pages which are infected and i cannot be attacked in that environment Win32 virus will hardly work in Dos environment. But thanks, your config sys and autoexec brings me to an idea that WLL is something which existed in Windows ME. This system was working on same base as win98 but it was masked as full Win32 system without dos base... I am sure that most people dont use DOS drivers with wll... and that may be the problem Normally i use dos driver for mouse, cdrom and soundcard. Dos games with all this glittering support and hardware work different as on PC speaker, without mouse and usually cracked without video... In some very special cases i can use lancard to see if and how dos games support IPX or TCP protocol. also for these reasons i use emm386 and because i have toomuch ram i use XMSDSK. and maybe this all stuff makes wll sick.
  11. i have resolved the problems on my own system. The freezing during bootup was caused by low buffers value (!!!). Originally i had buffers set to 99,8 - largest possible value. with it system worked, and i did not measured or recognized any issues with performance. Thats quite strange, because reccomended value was always around 20, and files around 100-150... I have files and buffers at topmost values and the system works as swiss clock. Because of issue with wll i set down the buffers size to 20. that fixed issue when wll wont load logo and dropped to dos. quite strange for an app of this type. With this setting i was able to run for some period, later i recognized errors during bootup - mostly freezing at usb device at first boot, and later after bios changes freezing with sound card. i thought that freezing of sound was caused by wll, but it did not fix after i removed wll. I set Buffers back to 99.8 and the system works again flawlessly. The reasons of this very strange behaviour are mystery for me. most users experienced problems with high values of buffers and this is first time i experienced opposite behaviour. since my computer is far behind standards i describe the HW config. maybe you shall see something what can help you. Abit VH6-T "Immolator" (modded bios, all hidden settings unlocked - specially acpi, added logo) Intel Pentium III-S 1,260 Mhz @ 1,482 Mhz, 512kb cache PQI SDRam 133@156 Mhz, 3x 512Mb sticks - Same series Asus Radeon x850XT 256Mb Ram LeadTech Winfast DTV2000h Tv tuner Creative SoundBlaster LIVE! 5.1 (dos and windows driver) Adaptec 19160 SCSI controller (scanner and harddisk) STLab USB2.0/Firewire controller Intel Pro 10/1000 GT Lan Card here is autoexec bat: @echo off cls @CTTY NUL LFNFOR ON mode con codepage prepare=((852) C:\OS\COMMAND\ega.cpi) mode con codepage select=852 lh keyb sl,,C:\OS\COMMAND\keybrd2.sys c:\dos\xmsdsk\xmsdsk.exe 513732 K: /c1 /t /y rem c:\dos\xmsdsk\xmsdsk.exe 524288 K: /c1 /t /y rem C:\OS\COMMAND\label K: scorpion lh C:\dos\blaster\sbeinit.com c:\dos\shsucdx.com /d:AADVARK /Q /l:f c:\dos\cmouse\ctmouse.exe rem lh c:\dos\lsl rem c:\dos\e1000odi rem c:\dos\e1000pkt 0x60 rem c:\dos\ipxodi.com /a rem lh vc rem c:\umbpci\fastvid\fastvid.exe 111 -128 d0000000 SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1 c:\dos\umbpci\umbfill.com CTTY CON and config sys: SWITCHES=/F /E DOS=HIGH,UMB,noAUTO FILEShigh=255 FILES=255 BUFFERShigh=99,8 BUFFERS=99,8 LASTDRIVE=k FCBShigh=1,0 FCBS=1,0 STACKShigh=0,0 STACKS=0,0 DEVICE=C:\OS\HIMEM.SYS /numhandles=128 /hmain=64 /TESTMEM:OFF /Q DEVICE=C:\dos\EMM386.EXE RAM NOTR SET PATH=C:\OS;C:\OS\COMMAND;c:\vc;C:\DOS SET BLASTER=A240 I7 D3 SET CTSYN=C:\OS DEVICEhigh=C:\DOS\QCDROM.SYS /D:AADVARK rem SHELL=C:\COMMAND.COM C:\ /E:1280 /L:160 /U:160 /P /F ACCDATE=C- D- E- F- DEVICEhigh=C:\OS\SETVER.EXE DEVICEhigh=C:\OS\IFSHLP.SYS devicehigh=C:\OS\COMMAND\DISPLAY.SYS con=(ega,,1) Country=421,852,C:\OS\COMMAND\country.sys try to test WLL with some really mad buffers and files values and watch its behaviour. for me is this only config where system works without trouble, but the wll with this config just wont run.
  12. to marius: i have tested it too now. with FAT32 and with patch from LLX i was able to create 4,294,918,144 mb, with NTFS and with patch from LLX i was able to create 4,294,918,144 bytes long file. so if we are thinking about additional filesystems kernel has to be upgraded... while i have here the demos i try other FS. definitely no change at all... i try again the disk internals driver. but i fear that it shall not help.
  13. yes they can, but small amount of video and audio is lost - few miliseconds - when the video is being captured from tv tuner. as i know there are possibilities how to fix it in video muxer but nobody tried it because NTFS was available. right now i have installed Paragon EXT2FSAnywhere shareware. i have some disks here to i try to format them and later mount. then i shall see if i will be able to capture files larger than 4gb, and the question is how large they can be
  14. one important thing. with wll system frozen on usb device previously. now it has frozen on soundcard. i changed some things in bios... as i mentioned before wll is very unpredictable. all i know is that with large ram, many devices it may cause freezing. without wll system boots correctly. always. wll makes my system more likely to freeze during bootup, and maybe it is responsible for some other things which happened last days on my system... this is report for Tihiys patched wll. i have to rebuild my computer to fix all possible mechanical problems (i added some cards to it and i want to mount them so tight as possible). if the problems persists i still cannot use wll.
  15. my system now show signs that source of some problems may be mechanical. Until those problems shall be fixed my bugreports are usable only partially. right now i am sure that freezing during bootup is caused by wll, and USB device card is only catalyst of the problem (many shared IRQs). also my settings in config sys regarding to buffers shows that maximum buffer value does not work correctly with wll.
  16. can be your wlll used with standard unpatched io and command com from win98se (or older systems such as win95)? i am asking because i want to keep my slovak (not czech) files...
  17. i have tried your package with instwll.bat and your logo sys... the behaviour described is linked with this type of installation... from the previous post i thought you have imported to tihiys wll your code... if not sorry. i have read readme.txt from your package and have done all as described there and the result is that freezing behaviour...
  18. so the first complete test of svgacom... (actual version) at first reboot the logo appeared normally, but later the image corrupted (maybe due my graphics card). system freezed On second same behaviour but system booted sucessfully. on third no logo appeared on fourth logo appeared but freezed without corruption but system freeezed... i have no point where i can indentify the problem. two problems regarding original and tihiys wll appeared - buffers and graphic driver...
  19. i started again my search for FAT32 alternatives. read this: http://www.911cd.net/forums//lofiversion/i...php?t13056.html there are a lot of possible solutions... hmmm: http://www.tucows.com/preview/247503
  20. bootlogo updated. i hope for the last time
  21. for now i have only tested tihiys version, and base version from RP pack, because i had even trouble to get wll work correctly. now i have to re-read whole topic here because i miss some info (i forget it) how to get work svgacom along with wll.
  22. i have identified one trouble: when i turn on the computer for the first time (turn on power button), system will surely freeze during bootup while using wll. after next reset (with reset button) it will boot correctly. Reason still unknown all i know that system will freeze at same line in bootlog: [0009456D] Starting Hlavný rozbočovač USB (USB\ROOT_HUB\PCI&VEN_1106&DEV_3038&SUBSYS_30381106&REV_62&BUS_00&DEV_09&FUNC_01) i try some bios settings to fix this. maybe related with irq, while this device use large amount of them. fixed: i have set IRQ in BIOS for usb...
  23. i did not found larger logo and upscaling is not the quality way... the image was too choppy then. Velvet maybe will change in near future - including the progress bar (dark red or silver maybe). I just want to have theme which is fully Win98 and looks as created for one system... When Wll is not used the usb will load correctly, but... i bought the USB2.0/Firewire combo just two weeks ago. it worked without trouble. Since Immolator is still some kind of experiment i cant hardly say that the driver was not the reason of this... In recent days i did some crash tests. First of them was keeping machine running without forced reboot. this worked. also i reinstalled some drivers - especially sound card to see if it affect stability. Also SVGACOM crash and fact that all values in my config sys are really mad right now i am sure that Buffers=99,8 cause that wll will drop to dos without loading logo and later windows and maybe freezing is caused by wll. it happened only today when i sucessfully used wll on my system, and never before... (logo updated a bit )
  24. 256 color version has been just released wait a minute or two... ... http://slayershrine.wz.cz/logo1.bmp 24bit color version. also system has frozen again during reboot. logo was ok in this case - again system has frozen in same place when usb was initialising...
  25. bootlogo for wll. Tihiy did great work with his loading image, but i like more old win98 instead of XP logo For people who want to look is here the link: http://slayershrine.wz.cz/logo.sys (shutting down logo is being created right now)
×
×
  • Create New...