Read Sharp UP-X300 (serv.man50) FAQ online
1.27 The X300 will only allow so many items then displays
insufficient memory
Q. The message “Insufficient memory item entry overflow” appears after
entering lots of items on one transaction or on one table.
insufficient memory
Q. The message “Insufficient memory item entry overflow” appears after
entering lots of items on one transaction or on one table.
A. This was due to the settings within mfull.ini, the MaxRegBuffer was set too
low, to change the registration buffer to allow more items per transaction
please edit the mfull.ini file as detailed:
1.
low, to change the registration buffer to allow more items per transaction
please edit the mfull.ini file as detailed:
1.
Perform SHUTDOWN on X300, 2. Tap screen 20 times, 3. Open wordpad
and edit \Hard Disk2\X300\Windows\Mfull.ini
1.28 Terminals “Freezing or locking out”
Q. The X300 terminals were taking long to respond to any key entry and it
seemed that they were froze or locked out.
Q. The X300 terminals were taking long to respond to any key entry and it
seemed that they were froze or locked out.
A. This particular incident was being caused by power to the Hub being
disrupted or intermittently disconnected, a UPS was used for power protection
to the HUB, the problem was resolved.
disrupted or intermittently disconnected, a UPS was used for power protection
to the HUB, the problem was resolved.
1.29 Terminals “Freezing or locking out”
Q. The X300 terminals were taking long to respond to any key entry and it
seemed that they were froze or locked out.
Q. The X300 terminals were taking long to respond to any key entry and it
seemed that they were froze or locked out.
A. This particular incident was being caused by power to the Wireless AP
being disrupted or intermittently disconnected, a UPS was used for power
protection to the AP, the problem was resolved.
being disrupted or intermittently disconnected, a UPS was used for power
protection to the AP, the problem was resolved.
1.30
The data (keyboard layout) reverts to old data on Client
Q. The X300 keyboard layouts were not the same as programmed on the
Master Terminal.
Master Terminal.
A. This was because the system had an old mlist.dat file that was copied from
another Till. This mlist file had old data to download but the terminal
configuration was different to the new system. (different number of terminals
in list)
Please delete mlist.dat from the PRESET folder, any changes made at the
Master will now be downloaded.
another Till. This mlist file had old data to download but the terminal
configuration was different to the new system. (different number of terminals
in list)
Please delete mlist.dat from the PRESET folder, any changes made at the
Master will now be downloaded.
1.31 Program data reverts to old data on Master after performing
Regenerate Terminal Database
Q. This was exactly the same situation as above.
Regenerate Terminal Database
Q. This was exactly the same situation as above.
A. Please refer to answer 1.30, delete mlist and mtablelist if they are above
zero size the system will automatically recreate these files
zero size the system will automatically recreate these files
1.32 Slower when busy. (V1.6.0.13)
Q. The E/User reported that the system went slow during busy periods.
Q. The E/User reported that the system went slow during busy periods.
A. After much checking it was found that the network cable (poor crimping of
RJ45 box) was found to be the cause.
RJ45 box) was found to be the cause.
Click on the first or last page to see other UP-X300 (serv.man50) service manuals if exist.