I tried 3.09b on RB133c and it's very bad.

I think that RB133c is suitable only as client and in this time we need only "station-pseudo bridge" mode on it.

Why you don't make separate "lite" version for RB133c?
Download page is prepared for it.
Then make real full-package for RB133c with only basic packages as wireless, system, security, routerboard.
And make it for RB with less memory.

you can already download the 'separate packages' file and install only system and wireless. it's up to you what you want in there, maybe some people need different features

Hi All!

I tryout install separated package on rb 133. Routeros: 3.0beta10.
Package: system + wireless, but the rb 133 not working.
If I install the system package alone, then RB 133 works fine.

Why? Wireless package have bugs?

Steve

Hi All!

I tryout install separated package on rb 133. Routeros: 3.0beta10.
Package: system + wireless, but the rb 133 not working.
If I install the system package alone, then RB 133 works fine.

Why? Wireless package have bugs?

Steve

what symphtoms you have when you have these two packages installed?

Hello,

I just updated two RB133c with Level 4 to V3Beta10. Now the boards boots, send the post-screen on the Hyperterminal, beeps one time, ask for the User/Password, send the Mikrotik Logo and thats it. Completly hang up until I repower the board and everthing started again. If you scan via Winbox, you don´t find the board. Both boards have now the same error and are useless for me. Before the update they worked fine with 2.9.42.

What now ?

Sometime patience helps. I waited longer (30 Minutes) and removed the WLAN Card, enable only routerOS, Routerboard security system and wireless and it boots with 3.0 Beta 10. Sorry, if I "produced" a little work with that. Hopefully I am able to reset the on-the-roof-already-installed-antenna with climing on this roof (25 meters).

For the record, I have somewhere in the neighborhood of 12 RB133c's deployed as low-volume access points and even some for point to point links with no issues. I just hate having to upgrade the license. Other than that they work flawlessly.

yet another same problem here; wehrhard; i have been spending hours here! the only thing is continious restars ! bdw my install was full package; actually 2.9 was doing fine; but i need to bridge station mode wlan to ethernet;

solved; unplug the mini-pci ; connect via serial before it starts to boot pres any key to enter bios; reset device; arter reboot you have brand new rb with router os 3.0beta9

solved; unplug the mini-pci ; connect via serial before it starts to boot pres any key to enter bios; reset device; arter reboot you have brand new rb with router os 3.0beta9

NO ITS NOT!! when i try to log in via winbox; faced an `can not locate routeros.dll!` ; and device continously restarts itself! cant see the device in netinstall!

basicly ` I NEED HELP!`

now i cant get to the bios ! comp freezez whenever i press a button over serial ! kinda stuck !!

ok, solution:

unlike the flow control=hardware in v2.9 ; v3.0 requires flow control set to Xon/Xoff , when you change and login over serial no freezing occurs. Once you change the boot to ethernet, install the v3.0 via netinstall , rb133c running as usual.