I downgraded from 3.0rc1 back to 2.95 and when it restarted , the system halts
I pluged in via serial for netiinstall thinking that would fix it and i get this error

RouterBoard 133C3

CPU frequency: 175 MHz
Memory size: 16 MB

Press any key within 2 seconds to enter setup..
kernel not found
trying bootp protocol... OK
Got IP address: 192.168.2.222
resolved mac address 00:13:8F:73:E7:C2
transfer started ..................... transfer ok, time=2.23s
setting up elf image... OK
jumping to kernel code
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


I tryed to upgrade the firmware via serial and it gives me the same thing, any ideas plz plz

try to format nand and do netinstall

Thats a great idea, been ther done that though. I think the thing is that netinstall is a pos. It doesnt see any of my 133cs, and yes i gave it a differnet ip than my workstation and hooked them both up to a seperate switch, brand new 133c out of the box that works fine , yet when i try to see it via netinstall i get that VFS kernel crash thing. Im using the new version of netinstall on windows xp and it just dont work worth a crap. It doesnt matter what i do , set my ip , go dhcp, and the earlier versioins dont work either , any other ideas

Thats a great idea, been ther done that though. I think the thing is that netinstall is a pos. It doesnt see any of my 133cs,

If you just open the program while your router is in the same network as the PC it might still take half an hour or so before the router pops up.

If you set netboot server in the netinstall and in console you go into the setup menu and choose "o" (Boot option) followed by "e" (Ethernet boot) the by pressing "x" next your router will boot through the netboot server and after that will immediately pop up in the netinstall screen....

Try that.

P.S.
I just found MT put this weekend a new netinstall on their website. (http://www.mikrotik.com/download/netinstall-3.3.zip)

Rudy

Na im using netinstall via serial null modem cable, the problem was the boot loader was old in the 133 , had to go to routerboard .com and upgrade the firmware, Ty for the reply though

Upgrade routerboard firmware from routerboard.com via serial console (Xmodem) and then install routeros via netinstall .