KPeter

Please, do not block me, if I am on the wrong forum page for FujiNet. The "Support-FujiNet" link directed me here from https://fujinet.online/support/. My question is: Why the Fujinet-flasher is not able to find COM - port on my Desktop PC with W'7 if it can recognize it without problems on small Cube-PC with W'7? Also, it is not working on Laptop with W'10. I tried lots of system settings (like Administrator), without results. My next question is: I am receiving notification from AtariAge about ubdates. I can see new features there, using PC to organize my setups for ATARI (?) How can I get there? It is nice to see it, but no link to access to that pages. Is somewhere a link for it? Why it is not in the e-mail notification? Thanks, Peter

Hmmm, I am not a frequent visitor of AtariAge to easily navigate, which type of issue where belongs. Can be answered my question simply there where I asked for? Thank you, and sorry for confusion. Peter

Sorry to go this page. I unsuccessfully tried to access from my e-mail to the actual page. The issue is with the latest FujiNet update. After update it can access to the website showing folders like usually, but I am not able to open any folders except my SD card inserted to FujiNet. Trying to open any other the yellow light (right-top) is not flashing just light solid. No sound, no action. ... FujiNet Version: 0.5.ed9d13bd Version Date/Time: 2021-03-15 00:55:47 Build Date/Time: Mon Mar 15 03:32:59 UTC 2021 Peter

Thanks, ... is it written somewhere ? Additionally ... AUTOEXEC.BAT is correctly loaded from SIDE3's SD Card despite of what is the PBI BIOS setting ... So ???

Thanks, ... is it written somewhere ?

RAMDISK.SYS v. BASIC XE 4.2 (or BASIC XE 4.1) issue. Previously here I mentioned an issue with BASIC XE using its Extension File of BASICXE.OSS, when running of BASIC XE from SDX with CAR command in many cases ATARI freezes, only Cold start helps. With some mods in SDX 4.49e it seemingly was eliminated only for the first using of CAR command. Running BASIC XE using again CAR commands, leads to the same issue. ... finally the reason was found Experimenting with CONFIG.SYS configuration I found, the BASIC XE issue is related to RAMDISK.SYS used w/o parameters. Removing DEVICE RAMDISK.SYS from Config.sys this isseue is gone. Peter

I found a strange behavior with CONFIG.SYS. (SIDE3 Cartridge) If in U1MB the setup is the following: 1. SpartaDOS X: Disabled 2. PBI BIOS: : Disabled 3. D1: configured from SIDE3's SD Card (including CONFIG.SYS and AUTOEXEC.BAT ) The system boot is starting with CONFIG.SYS from CAR: drive, ignoring CONFIG.SYS on D1: drive but using AUTOEXEC.BAT from D1: 3. D1: configured from SIO2SD or SIO2PC (including CONFIG.SYS and AUTOEXEC.BAT ) SpartaDOS 4.49e is using CONFIG.SYS and AUTOEXEC.BAT from D1:, ignoring CONFIG.SYS on CAR: 1. SpartaDOS X: Disabled 2. PBI BIOS: : Enabled 3. D1: configured from SIDE3's SD Card or SIO2SD or SIO2PC (all including CONFIG.SYS and AUTOEXEC.BAT ) SpartaDOS 4.49e is using CONFIG.SYS and AUTOEXEC.BAT from D1:, ignoring CONFIG.SYS on CAR: Is it right?! Peter

Not stable boot of SIDE3's SDX 4.49e. Despite of SpartaDOS is disabled in U1MB, ATARI is randomly booting from U1MB's SpartaDOS 4.49. It happens in booth cases: PBI BIOS is Enabled or Disabled and if D1: is SDX Formatted HD. More frequent is this behavior in Disabled PBI BIOS status. If D1: is DOS 2.x or MyDOS it starts booting that OS-s. If ATARI is booting with Boot Error message (with SDX formatted disk in D1:) it needs to push SIDE3 Reset Button + ATARI Reset Button to boot from SIDE3 the SDX 4.49e. It differs from SIDE2 cartridge where ATARI is booting always from SIDE2's SDX ... if switch is down. Is that SIDE3's "behavior" standard or waiting for some update of SIDE3 or SDX 4.49e ? I have flashed the latest updates in U1MB and SIDE3. Thank you, Peter

Yes, it is correct. I forgot to mention FujiNet like a real source ... sorry. I just was experimenting with it and seeing issues I removed it from the SIO chain. The issues are a "litle" disturbing. Peter

Right. I copied FujiNet files on an SD drive and use CONFIG.COM to start FujiNet. Generally, using FujiNet from U1MB or any SIDE cartridges has lots of issues ... need some more developments. Peter

Hmmm, FujiNet makes me headache also. It tries to push its ROM drive like D1: ... I could not find for now, how to correctly configure together (w/o) SIDE3 or U1MB. At some U1MB configuration it says SIO conflict (or something similar). But, without FujiNet I never experienced loosing APT or FDISK. Peter

I updated my FujiNet today. Unfortunately it does not work. With version before I could start it from SpartaDOS X - of course, with no success, but after that went back to the SDX command line. Now ATARI freezes, just Reset can restart it. Still I am waiting for extending of characters to the special, like | . I saw C code modification day, after I reported this issue a month ago, but this correction is still not in updates (at least in 2 next after my report). Again: If my password includes | character it works like EOL or some text separator in the password. Characters after this are interpreted like file name ... Please, correct this character issue. To change password in my home's network system is a big issue for its complexity and number of attached equipment on wifi ... So, the only way to extend the character-set accepted by the password on FujiNet. Thanks you, Peter

Just for sure. In the ZIP file there is a SDX449e.ROM file. What is the XEX is doing during flash process with this ROM file? If I start flasher, I can see only a few (4?) lines (maybe 64kB altogether flashed?) written on monitor. Thank you, Peter

It works. 1. SIDE3 does not remember Config setup, from SPARTA.DOS folder, where are the XXXXX.CFG configuration files. 2. Cold start or starting CAR from SIDE3 needs to use SIDE3-RESET followed by ATARI-RESET to load SpartaDOS 4.49e from SIDE3. Otherwise ATARI is not starting. Peter

Great! Unfortunately it looks like I have broken FujiNet device, could I expect, the manufacturer will replace it with a good one and with the correct solution of SIO IN? Finally I helped on this case and I notified the manufacturer about it also, he said, it will be better to give my idea to the designers ... so, I am expecting some credit for it ... Peter

I guess, it is not my case. I verified full functionality of my all USB cables. I can download/upload files to my cellphone(s), so, there are more than +5V & GND line there. Despite, the manufacturer says, all devices are tested before selling, I suspect, my was not, otherwise it should work. I watched lots of videos, how it works, the connection to the net looks very simple, if the device is OK. How I wrote, I made sure, I have 2.4GHz WiFii set up, despite of it and the strong signal, "Connect fails". Peter

Good question. I never had any issue with that type of USB cables. So, I should ask differently. Is the length of cable and from that the impedance is the issue or different pinouts /missing connection ? Please, concretely specify the source the possible issue. No, It is not about supplying the FujiNet from USB or ATARI +5V. It is about (how I saw on the FujiNet pages schematic) SIO Input directly connected to ATARI SIO Port. Of course, if the S4 is OFF, no external PS (consequently no internal +3.3V) connected to FujiNet, but through SIO In pin an ATARI's Pull-Up resitor or some circuitry is incorrectly back-supplying an OUTPUT circuitry on ESP32. I guess, it is a not correct solution, in good design not permitted. What I wrote, there should be also a controlled switch (analog-switch from DG series- Maxim, ... etc.) what separates ESP32 output from ATARI's SIO Input. ... Just like an example of Analog Switch: https://www.mouser.com/datasheet/2/427/dg3257-1766310.pdf The whole solution does not need big modification, and the switch can be controlled from Voltage on U3.1 pin. That solution will disable the ticking noise. Peter

I got similar message after unsuccessful installing driver for FujiNet on W'7. On W'10 Laptop the system did not react on connection of USB cable. So, I cannot install any update. My connection is failing despite of correct setup the WiFi for 2.4GHz. ... I am really confused with it. The next thing is the ticking noise when the switch is OFF. Checking the schematic (I do not know, it is the right one) it looks like the SIO connections are not correctly designed. When Vin is disconnected, parallel with it, that ports should be separated by an analog-switch, controlled by the switch on side of box. It is not complicated and I am surprised it was not solved on the beginning Peter

I have also FujiNet with firmware from 2-3 weeks (bought that time), but using it with SIDE2/3 is not really good. It has its own D1: drive in ROM and it is conflicting with D1: drive of other units. The result is not complete list of files (any new DIR commands gives different listing of files). I temporary disconnected FujiNet from SIO port because the attempt of updating of its firmware crashed on wrongly installed driver on W'7 or not installing on W'10. So, I am not able to experiment with it. The main issue is despite of list of WiFi around me and strong signal from my own, it is not able to connect to the net. ... Maybe the update will correct this issue and also the issue with co-existence with SIDE cartridges. Peter

With SIDE3 I experienced the following: 1. Setup of U1MB: a) SpartaDOS: Disabled; b) PBI BIOS and HD: Enabled Cold Boot (by ATARI Switch) or from SIDE3 Loader starting CAR or ROM file, ATARI starts with: a) rolling "BOOT Error" on monitor; if D1: is defined from SIDE3 SD card b) One line on top of monitor: "SpartaDOS X not present" in case of a) and b) only SIDE3-Reset -> ATARI-Reset sequence will initialize the SpartaDOS 4.49e c) If D1: is SIO2SD/PC and the ATR file on it, any of ATARI DOS II V2.5 or MyDOS will start correctly from any type of Cold Starts, but DOS 2.x (x<5) will not, the system crashes and only (ATARI Switch OFF/ON) Cold Start helps ( a), b), c) ) To start ATR image file with DOS 2.0s correctly happened just once from many of tries to reboot system. Of course, the disk DOS 2.0s is visible from SpartaDOS, MyDOS or ATARI DOS II V2.5 on Dx: (x>1) d) All programs XEX, COM ... from ATR image file are working correctly *) (see bellow list of them) MEM /X shows: ------------------------------------------------------------------------- Main: $1358, $1358, $0000 Ext: $7294, $7294, $0000 Use: Banked, PortB $0D Top: $9C1F ($BC1F), $7FFF Free : 35015 (43207), 3435 64 banks total (1024KB) 4 banks free 2. Setup of U1MB: a) SpartaDOS: Disabled; b) PBI BIOS and HD: Disabled Cold Boot (by ATARI Switch) or from SIDE3 Loader starting CAR or ROM file, ATARI starts correctly From all tested programs *) the Turbo BASIC XL 3.2q cannot start: Error 179 - Memory conflict Of course the memory occupation by SDX different is there: MEM /X shows: ------------------------------------------------------------------------------- Main: $1958, $1958, $0000 Ext: $7294, $7294, $0000 Use: Banked, PortB $0D Top: $9C1F ($BC1F), $7FFF Free : 33479 (41671), 1194 64 banks total (1024KB) 4 banks free =================================================== Unfortunately with BIOS logo: "Boot" or "Power on" the boot drive selection is not working Selecting any from D2: - DO: results only boot from D1: (MyDOS, DOS 2.5), nothing else [L] selection is OK, going to SIDE3 Loader. 3. SIDE3 does not remember CONFIG file selection like SIDE2 does. =================================================== *) Tested programs loaded from ATR disk images: 1. EASM 2. CLSN Pascal 3. Microsoft Basic 1.0 (includes all functions of MS Basic 2.0 from its Extension file!) 4. LISP 5. Analog Database 6. Macro Assembler Editor 7. ATARI Basic 8. ATMAS II 9. ACTION! V3.7X build 30.06.2015 22:08 10. Turbo Basic XL 3.2q (see notes under 1. and 2.) 11. FastBasic Peter

Yes, probably Jon blocked my email account on last weekend. ... Hmmm. And yes also, Frankie helped me. Thank you Trub, you are not ignoring my information. My intention is always to give info from my findings to help for improvements. Not blaming or humiliating people. Peter

Yes, the latest update works perfectly, when the SDX 4.49e starts up. I do not see any issue related to TD. BASIC XE 4.2 runs perfectly with its extension file also. I tested all my standardly used software for verification of functionality. For now, everything looks fine. But still there is the "glitch" with cold start from turned of ATARI by switch or activating CAR-tridges from SIDE3 LOADER. It needs sequence of Reset on SIDE3 plus Reset on ATARI to start SDX 4.49e initialization. If D1: is from SIDE3 SD card, ATARI starts with rolling BOOT ERRORs on monitor. If D1: is from SIO2SD/SIO2PC and the disk is SpartaDos formatted, it starts with error message signalizing no SpartaDos present. If the disk formatted with some of DOS 2.X, it is not booting correctly, the picture is black with blinking characters and only the OFF/ON switch can restart ATARI. It is just for info from my latest tests. Peter

If it works, like shown on the picture, the mods look promising Peter

Thank you Jon ... I hope. Peter